Forum Discussion

albatroz19's avatar
albatroz19
Level 5
24 days ago

Netbackup Catalog backup growing

Hi,
in our environment we have a primary server with a catalog backup stabilized about 650Gb size with 2 week retention.
By few days it's growing and backup passed from 650GB to 930Gb and now to 1,1Tb by day. No particular actions performed on primary server, on the contrary we dismissed some client.

How can i check, why the catalog backup growing up very fast in last days?

Any suggestion is very appreciated.

Thanks,

  • Hi,
    thanks for support. I don't know how it was possible but now the Catalog backup is returned about ~600Gb, and no actions performed by me.....

    Regards,

    • mph999's avatar
      mph999
      Level 6

      Nope, me neither ...
      Let's put it down to mice with poor IT skills ...

  • Hi,
    the primary server is Linux RHEL 6.10 (Santiago), and NBU 8.3.0.2.
    By your answer, how can i check catalog compression has been disabled and maybe was activated, or images unarchived?

    Thanks and Regards,

    • mph999's avatar
      mph999
      Level 6

      Have a look at the bpcatlist command

      https://www.veritas.com/support/en_US/article.100016710

  • You don't mention the OS of the Primary Server but the suggestions are the same for both Win / Linux.

    If the catalog is usually ~650GB consistently, then images that expire = new backups, so to almost double in size in just a few days is odd.

    First step is to do a recursive listing of /usr/openv/netbackup/db/images (or ...\veritas\netbackup\db\images ) and look at the size of files, what is 'big' that has appeared in the past few days ?

    The dir structure under images will show multiple client names
    Under each of these you will have subdirectories of ctime, 1 million seconds apart

    Example:
    /usr/openv/netbackup/db/images/reanbur630-02/1726000000
    /usr/openv/netbackup/db/images/reanbur630-02/1727000000
    /usr/openv/netbackup/db/images/reanbur630-02/1728000000

    Under each of these you should have just .f files and .lck files, as well as a catstore dir which depending on backup size will contain around 10 files per image that is greater than a certain size (I forget the exact size, but if the .f file is > than I think 2GB it gets truncated to 72 bytes and the contents are split up into the multiple files in catstore - this is to make large backups more efficient to search.  The files under catstore will contain the ctime of the image as part of their filename).

    There shouldn't be any other files - although if you have catalog compression, the files will be compressed.

    Actually that's a thought, were you using catalog compression and it has been disabled perhaps, or catalog archiving and images have been unarchived ?