Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ Administrator's Guide, Volume I
  3. Section V. Configuring backups
  4. Protecting the NetBackup catalog
  5. Parts of the NetBackup catalog
  6. About the NetBackup image database
  7. About NetBackup image .f files
Veritas NetBackup™ Administrator's Guide, Volume I

About NetBackup image .f files

The binary catalog contains one or more image .f files. This type of file is also referred to as a files-file. The image .f file may be large because it contains the detailed backup selection list for each file backup. Generally, image files range in size from 1 kilobyte to 10 gigabytes.

The .f files are found in the following location:

Windows: install_path\NetBackup\db\images\clientname\ctime

UNIX: /usr/openv/netbackup/db/images/clientname/ctime/

The file layout determines whether the catalog contains one .f file or many .f files. NetBackup configures the file layout automatically, based on the size of the binary catalog. NetBackup uses one of two layouts: single file layout or multiple file layout.

  • Image .f file single file layout

    NetBackup stores file information in a single image.f file if the information for the catalog is less than 100 megabytes.

    When the backup file of one catalog backup is less than 100 megabytes, NetBackup stores the information in a single image.f file. The image.f file is always greater than or equal to 72 bytes, but less than 100 megabytes.

    The following is a UNIX example of an .f file in a single file layout:

    -rw------- 1 root other   979483 Aug 29 12:23 test_1030638194_FULL.f
  • Image .f file multiple file layout

    When the file information for one catalog backup is greater than 100 megabytes, the information is stored in multiple .f files: one main image .f file plus nine additional .f files.

    Separating the additional .f files from the image .f file and storing the files in the catstore directory improves performance while writing to the catalog.

    The main image.f file is always exactly 72 bytes.

    -rw- 1 root other      72 Aug 30 00:40 test_1030680524_INCR.f
    -rw- 1 root other     804 Aug 30 00:08 catstore/test_1030680524_INCR.f-list
    -rw- 1 root other 1489728 Aug 30 00:39 catstore/test_1030680524_INCR.f_imgDir0
    -rw- 1 root other       0 Aug 30 00:40 catstore/test_1030680524_INCR.f_imgExtraObj0
    -rw- 1 root other 1280176 Aug 30 00:39 catstore/test_1030680524_INCR.f_imgFile0
    -rw- 1 root other     192 Aug 30 00:40 catstore/test_1030680524_INCR.f_imgHeader0
    -rw- 1 root other       0 Aug 30 00:40 catstore/test_1030680524_INCR.f_imgNDMP0
    -rw- 1 root other 9112680 Aug 30 00:39 catstore/test_1030680524_INCR.f_imgRecord0
    -rw- 1 root other 2111864 Aug 30 00:39 catstore/test_1030680524_INCR.f_imgStrings0
    -rw- 1 root other      11 Aug 30 00:40 catstore/test_1030680524_INCR.f_imgUserGroupNames0

Feedback

Was this page helpful?
Previous

About NetBackup image files

Next

About the catalog backup of cloud configuration files

Feedback

Was this page helpful?