Forum Discussion

dugga's avatar
dugga
Level 4
9 years ago
Solved

Netbackup appliance : Log Partition usage crossed 95%

 

Hi all,

I'm getting the following alerts from one for the netbackup appliance , this is our media server

I have enabled logging to max, now i started getting alerts that its growing and it is almost 95% full.

From where can cleanup these logs in the cli; kindly help if there is any procedure or article on how to clean up this partition.

+-----------------------------------------------------------------------------+
|                            Partition Information                            |
|+---------------------------------------------------------------------------+|
||ID |  Partition  |  Total  | Used |  Status   |   State   |  Acknowledge   ||
||---+-------------+---------+------+-----------+-----------+----------------||
||5  |Log          |184 GB   |95 %  |Optimal    |Warning    |No              ||
||---------------------------------------------------------------------------||
|| * The value displayed here may be different from the backup space that is ||
|| available or used on the MSDP partition. The backup space statistics for  ||
||  the MSDP partition can be obtained by checking the MSDP disk pool sizes  ||
||                  from NetBackup Administration Console.                   ||
|+---------------------------------------------------------------------------+|
+-----------------------------------------------------------------------------+

  • ejporter's avatar
    ejporter
    9 years ago

    The /log/crash directory is where core dumps from programs that crash end up.   Some revs of netbackup have processes that core dump all to regularly.   You can pretty safely delete files from /log/core/ assuming you are not using them to debug a problem with netbackup.

    The /log/netbackup/ directory has a whole subset of directories.  These contain the traditional netbackup logs.  You can fairly safely clean up files in the subdirectories under /log/netbackup/.   Again you may want them to debug problems,   but you can not keep them all forever.   Go to /log/netbackup/ and run the du command again and you will see which directories to focus on in that area.   You also probably should look at how verbose you have the logging set.  You may want to turn it down a bit if it is set at a high level.

    Read more here on how to manage netbackup logs:  https://www.veritas.com/support/en_US/article.000108090

     

8 Replies

Sort By
    • dugga's avatar
      dugga
      Level 4
      9 years ago

      Our Master Server is at 7.6.0.3 and Media servers which are the 5220 Netbackup Appliance at 2.6.0.3

       

      I checked the /log/upload partition in the CLI by logging to the maintenance mode and could see a lot of files generated with the name format like : cmd_out_1489659883457351.log

       

      I did a vi and found this:

      s65013:/log/upload # vi cmd_out_1489659883457351.log
      Time Ran: Thu Mar 16 2017 11:24:43 CET
      CMD: LC_ALL=C /usr/bin/w3m -dump /tmp/9oWiCQD0gC.html
      RETVAL: 0
      STDOUT:


      Compute Node s65013

      Time Monitoring Ran: Thu Mar 16 2017 11:22:10 CET

      +-----------------------------------------------------------------------------+
      | Partition Information |
      |+---------------------------------------------------------------------------+|
      ||ID | Partition | Total | Used | Status | State | Acknowledge ||
      ||---+-------------+---------+------+-----------+-----------+----------------||
      ||5 |Log |184 GB |95 % |Optimal |Warning |No ||
      ||---------------------------------------------------------------------------||
      || * The value displayed here may be different from the backup space that is ||
      || available or used on the MSDP partition. The backup space statistics for ||
      || the MSDP partition can be obtained by checking the MSDP disk pool sizes ||
      || from NetBackup Administration Console. ||
      |+---------------------------------------------------------------------------+|
      +-----------------------------------------------------------------------------+

      STDERR:

      Not sure if these logs will be of use for any troubleshooting.

      Please let me know if I can just delete them.

      These version are out of support now.

      Recently i had set the logging to MAX in the master server to get more details when any backup is failed.

      I have attached the bp.conf file to here.

      Let me know if any information is required. 

       

      • quebek's avatar
        quebek
        Moderator
        9 years ago

        Hi

        My take is that majority of the /log is being used by netbackup subdirectory so /log/netbackup - you can go into this location and check this out by running from there

        du -sh *

        If I am mistaken run this command from /log this will allow you quickly figure out the 'guilty' one folder... and then take actions. Also when backups are failing only certain logs are needed - maybe you do not need all which are configured under /log/netbackup.... ask VRTS which should be enabled...

  • quebek's avatar
    quebek
    Moderator
    9 years ago

    Hey

    You need to clean up some NBU related logs located in /logs/netbackup directory. To do this please elevate to CLISH (https://www.veritas.com/support/en_US/article.000116864) and change to this dir and there run 

    du -sh *

    figure out which one is the biggest and if you dont need these logs remove them

    Also can you provide output form this command

    cat /usr/openv/netbackup/bp.conf  so we can see the debug levels etc...?