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
Veritas NetBackup™ Administrator's Guide, Volume I

Parts of the NetBackup catalog

The NetBackup catalog resides on the NetBackup master server. It manages and controls access to the following types of data:

  • Image metadata (information about backup images and copies (image header files)).

  • Backup content data (information about the folders, files, and the objects in a backup (.f files)).

  • NetBackup backup policies.

  • NetBackup licensing data.

  • The NetBackup error log.

  • The client database.

  • Cloud configuration files.

    See About the catalog backup of cloud configuration files.

The catalog consists of the following parts:

  • Relational database files.

    NetBackup uses the SQL Anywhere Relational Database Management System to store information in the NetBackup database (NBDB). The metadata includes information about the data that has been backed up, and about where the data is stored.

    See About the NetBackup relational database.

  • The image database.

    The image database contains information about the data that has been backed up.

    See About the NetBackup image database.

  • NetBackup configuration files.

    The configuration files (databases.conf and server.conf) are flat files that contain instructions for the SQL Anywhere daemon.

    See About the NetBackup server.conf file.

    See About the databases.conf file.

NetBackup is sensitive to the location of the master server components. Running any part of NetBackup (the binaries, the logs, the database, the images) on a network share (NFS, for example) can affect performance of even normal operations.

NetBackup can be CIFS-mounted on SAN or NAS storage as long as the average I/O service times remain less than 20 milliseconds.

The storage must also meet certain conditions to ensure the Sybase requirement for data integrity:

  • The order of file writes must be guaranteed.

  • When a write request is issued, the write must complete to the physical storage. The write request must not merely be buffered when the SAN or the NAS returns from the write call.

    See the following article for more information:

    http://www.veritas.com/docs/TECH158868

Figure: Catalog configuration on Windows computers

Catalog configuration on Windows computers

Figure: Catalog configuration on UNIX computers

Catalog configuration on UNIX computers

Feedback

Was this page helpful?
Previous

About the NetBackup catalog

Next

About the NetBackup relational database

Feedback

Was this page helpful?