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. IT Analytics Help
  3. Section XVI. System Administration
  4. Data Retention Periods for SDK Database Objects
  5. Data retention periods for SDK database objects

Data retention periods for SDK database objects

This section covers the procedure for modifying data retention periods for systems collected by Data Collectors deployed via the SDK.

Because data collection continuously adds data to the database, management of the database size becomes an essential task. For objects created via the SDK, a data retention period can be defined along with the database schema, to align with your IT Analytics reporting requirements. Data retention (purging rules) described in this section apply only to user-defined objects defined by an SDK project; API and database objects are handled by system parameters.

Purging rules (data retention periods) are specific to an object, such as array disk performance, and they are used to maintain corresponding database tables. These rules are configured at the beginning of the object's definition in the schema template json file.

Best Practice: Configure retention days for objects that accumulate historical data over time, such as array performance. Other objects should not have data retention days.

In multi-tenancy environments, where IT Analytics domains partition client data, data retention periods can be configured for each domain. The data retention period for a domain applies to that domain and all of its sub-domains. For systems collected by traditional Data Collectors, use the Data Retention tab located: Admin>Advanced>System Configuration.

To enable purging for a user-defined object for a specific domain, take the following steps.

  1. Log in to the Portal Server as user aptare.

  2. Type the following command:

    sqlplus <portal_user>/<portal_password>@//localhost:1521/scdb
    where <portal_user> and <portal_password> are portal credentials to connect to the database.
  3. At the command line, execute the following SQL statement, substituting relevant values for the variables shown < > in the syntax.

    See Find the domain ID and database table names.

    See Retention Period Update for Multi-Tenancy Environments Example.

    See Retention period update for SDK user-defined objects example.

    INSERT INTO apt_purge_rules (table_name, product_type, table_description, date_column_name, retention_days, default_retention_days, domain_id, creation_date, last_updated)
    SELECT table_name, product_type, table_description, date_column_name, <NewRetentionDays>, default_retention_days, <domain_id_value>, SYSDATE, SYSDATE
      FROM apt_purge_rules
     WHERE domain_id IS NULL
       AND table_name = <tableName>;
    Commit;

Feedback

Was this page helpful?
Previous

Data Retention Periods for SDK Database Objects

Next

Data aggregation

Feedback

Was this page helpful?