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™ for DB2 Administrator's Guide
  3. Configuring NetBackup for DB2
  4. Configuring the run-time environment
  5. Creating a db2.conf file (vendor method)
Veritas NetBackup™ for DB2 Administrator's Guide

Creating a db2.conf file (vendor method)

The NetBackup for DB2 configuration file, db2.conf, consists of a series of keywords and values. This file defines how to back up the database and the archive logs. It must be created on each NetBackup for DB2 client.

The installation package installed a file named db2.conf that you can customize. The following procedures show you how to customize this file. Follow the instructions in this section if you use the vendor method to perform backups.

To create a db2.conf file for use with the vendor method

  1. Before you create the db2.conf file, you need to create the policies to back up the configuration files.

  2. Log into a client computer.
  3. Copy the sample db2.conf file from its location in the sample directory to its active location.

    Its location in the sample directory is as follows:

    Windows: install_path\NetBackup\dbext\db2\samples

    UNIX: /usr/openv/netbackup/ext/db_ext/db2/scripts

    The active location for the db2.conf file is as follows:

    Windows: install_path\NetBackup\dbext\db2\db2.conf

    UNIX: $DB2_Instance_Home/db2.conf

  4. In the db2.conf file, create an object identifier for backing up the database.

    This object identifier starts with the following keyword lines:

    DATABASE SAMPLE
    OBJECTTYPE DATABASE
    . . .
  5. In the db2.conf file, create an object identifier for backing up the archive logs.
    DATABASE SAMPLE
    OBJECTTYPE ARCHIVE
    POLICY DB2_TYPE_POL_LOGPOL # a DB2 type policy
    SCHEDULE DEFAULT-APPLICATION-BACKUP

    In the POLICY line, specify the name of a DB2 policy. This policy can be the same policy that you use to back up the database.

    In the SCHEDULE line, specify a Default-Application-Backup schedule.

  6. You may need to add other entries to the db2.conf file.

  7. Save and close the db2.conf file.
  8. Repeat this procedure on each client computer.

More Information

Configuring a policy to back up the configuration files

Keywords for the db2.conf file

Example db2.conf file (vendor method)

Creating a db2.conf file for use with the user exit program

Example db2.conf file using ARCFUNC SAVE

Example db2.conf file using ARCFUNC COPY

Configuring the logon account for the NetBackup Client Service for NetBackup for DB2

Feedback

Was this page helpful?
Previous

Example db2.conf file using ARCFUNC COPY

Next

Example db2.conf file (vendor method)

Feedback

Was this page helpful?