Skip to main content
Question

Database Command Line - Retention/Data Aging

  • August 26, 2026
  • 1 reply
  • 27 views

Forum|alt.badge.img

Hello All,

I need some clarification regarding Storage Policy retention configurations for DB2, and Oracle command-line backups initiated through DB2 and RMAN commands. Version - 11.40

My understanding is that Commvault currently manages command-line log backups based only on days-based retention and not cycle-based retention. By Cycle, I am referring to the complete database backup chain consisting of Full + Incremental/Differential + Log backups as part of a cycle.

My first question is whether the cycle retention condition is applicable to Incremental/Differential/Delta backups initiated through the command line. It appears that it may be, but the behavior is not entirely clear.

In the case of Oracle, the situation is even less clear because archive log backups are also classified as Incremental backups. As a result, it is difficult to determine whether these log backups follow cycle-based retention or are retained solely according to the days-based retention settings.

If command-line database backups cannot reliably utilize cycle-based retention and instead must rely on days-based retention, what would be the recommended retention settings for both:

  • Command-line database backups
  • Command-line log backups

Any guidance on the recommended retention configuration and best practices for this use case would be greatly appreciated.

1 reply

Forum|alt.badge.img+17
  • Vaulter
  • August 27, 2026

Hi ​@Vivek Jayaraman ,

 

1. DB2 Command-Line Backups

  • Retention Behavior:

    • Incremental/Differential/Delta Backups:
      For DB2 command-line backups, cycle-based retention is applicable. Incremental and delta (differential) backups are dependent on the existence of a full backup.
      • If only one full backup exists, all subsequent incremental/delta backups are tied to it, and retention cycles are not satisfied until a new full backup is taken.
      • Data aging for command-line jobs: Command-line full and associated incremental/differential/log backups are pruned based on cycles. However, for third-party command-line backups, retention cycles are not used for copies involved in those operations; instead, data is aged according to the associated retention time (days-based retention).
      • Key Point: To ensure proper aging, you must perform periodic full command-line backups to satisfy the cycle requirement.
  • Recommended Retention Settings:

    • If you want to use cycle-based retention:
      Schedule regular full command-line backups (e.g., weekly) so that cycles can complete and older incrementals/deltas can age out.
    • If you rely on days-based retention:
      Set the retention period (in days) according to your recovery and compliance needs, understanding that cycles may not be honored for command-line jobs unless fulls are scheduled appropriately.
  • References:

2. Oracle Command-Line (RMAN) Backups

  • Retention Behavior:

    • Archive Log Backups:
      Archive log backups are considered incremental backups in Commvault.
      • For command-line (RMAN) initiated backups, retention is primarily days-based. Cycle-based retention is not reliably applied to command-line jobs.
      • Archive log backups are retained according to the days-based retention configured in the storage policy, not by backup chain cycles.
      • Key Point: If you require consistent chain-based retention, use Commvault-initiated backups (not pure RMAN command-line jobs).

Best Practices

  • DB2: Schedule regular full command-line backups to allow cycles to complete and enable proper aging of incrementals/deltas/logs.
  • Oracle: Use days-based retention for all command-line (RMAN) backups, including archive logs.
  • If you require cycle-based retention for compliance or recovery reasons, use Commvault-initiated backups instead of pure command-line jobs.

If you have a specific retention goal (e.g., 14 days, 2 cycles), set both values, but understand that for command-line jobs, days-based retention will be the primary mechanism unless you ensure regular fulls for DB2.

Documentation Links: