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. Using Snapshot Client with NetBackup for DB2
  4. About configuring NetBackup for DB2 block-level incremental backups on UNIX
  5. Storage Checkpoint configuration on the NetBackup for DB2 client
Veritas NetBackup™ for DB2 Administrator's Guide

Storage Checkpoint configuration on the NetBackup for DB2 client

By default, the NetBackup for DB2 with Snapshot Client for proxy BLI backups uses the Fulldata Storage Checkpoint. When Fulldata Storage Checkpoint is in effect, the NetBackup for DB2 agent keeps the DB2 database quiesced. The database is quiesced (write suspend) only for the time that is needed to create a Storage Checkpoint.

To change the default option to use Nodata Storage Checkpoint, a user must create the following file, which can remain empty:

    /usr/openv/netbackup/ext/db_ext/NODATA_CKPT_PROXY

If the agent finds this file during run time, it uses Nodata Storage Checkpoint, and it keeps the database containers in quiesced (write suspend). The database containers are kept in this mode for the duration of the backup.

Feedback

Was this page helpful?
Previous

Configuration requirements for BLI backups with NetBackup for DB2

Next

Configuring policies for BLI backups with NetBackup for DB2

Feedback

Was this page helpful?