Set quotas

Continuous Data end-of-life notice

Action required: The Continuous Data UI, API, and CLI are scheduled for end of life. Review the latest migration guidance and start planning your transition to Data Control Tower.

On new engine installations of 2026.5.0.0 and later, the Admin UI opens directly to the Performance Dashboard, and the Manage, Resources, and System menus are unavailable. Engines upgraded from an earlier version keep full Admin UI access. This restriction cannot be changed by customers; contact Delphix Support if you need it lifted temporarily.

Learn more about the Continuous Data end-of-life announcement.

This topic describes how to set quotas for database objects.

  1. Log into the Delphix Management application.

  2. Select Manage > Datasets.

  3. For setting a quota for a dataset, select the Configuration tab for the dataset. (For setting quota for a group, skip this step.)

  4. Select the Policies tab and from the Quota tile and select Customize this policy.

  5. In the Quota Policy window enter the amount of storage space you want to allocate for a quota.

  6. Click Save to set the amount.

Quotas and Low Space Errors

Be very careful setting quotas. As a group or virtual database (VDB) approaches the quota level, snapshots may fail and logs may not be captured, causing LogSync to fail.

Quota thresholds

The following is a table of the thresholds and a description of the actions taken at each threshold. This behavior is generic across all engines.

Thresholds

Default ranges

Actions taken

Critical

Quota ≥ 95%

  • Disable VDBs and dSources under quota (for a group quota, everything inside gets disabled).

  • Disallow jobs detailed in the DB actions table below.

  • Cancel all in-flight jobs listed in the DB actions table except for enabling.

  • Poll every minute.

Resume

95% > Quota ≥ 90%

  • VDBs and dSources disabled by critical quotas will not be automatically re-enabled (DBs can still be manually re-enabled).

  • Resume fault is triggered if the quota has fallen from the critical threshold and if a DB was disabled from hitting the critical threshold.

  • Warning fault is triggered.

  • Poll every 3 minutes.

Warning

90% > Quota ≥ 80%

  • Warning fault is triggered.

  • VDBs and dSources disabled from hitting critical quota will be re-enabled.

  • Poll every 3 minutes.

Safe

80% > Quota

  • VDBs and dSources disabled from hitting critical quota will be re-enabled.

  • Poll every 5 minutes.

If a DB was disabled prior to reaching the critical quota, it will not be automatically re-enabled when falling to an acceptable range or when the quota is removed.

Disallowed database actions when in quota critical threshold

Here is a table of the actions that are not allowed when the quota is in the critical threshold.

DB actions table

Target is group

Target is not group

  • Refresh target in the group.

  • Sync target in the group.

  • Link into the group.

  • Provision into the group.

  • Enable target in the group.

  • Refresh target in the group.

  • Sync target in the group.

  • Enable target in the group.

If a critical quota is placed on a target, dSources, and VDBs can still provision to groups that are quota below the critical threshold.