Skip to main content

Set quotas

A quota limits new protection and manual backups. When a project exceeds a limit, the service rejects new plans, resource additions, manual backups and moves to stronger policies. Existing scheduled backups continue.

Locked data counts toward storage usage until its lock expires. A project may therefore exceed its storage quota even after deleting backups. Project members can remove resources from plans where the policy permits, or ask you to increase the quota.

Quotas are off until you set a limit.

The three limits​

LimitCLIMeasures
Protected size--source-bytesThe provisioned size of everything the project's plans protect.
Protected resources--resourcesResources in the project's plans, each counted once.
Stored--stored-bytesThe project's footprint in the repositories, as the last sweep measured it.

Each limit comes from the narrowest scope that sets it. The order is the project, then its domain's default for projects, then the cloud's default. A limit left unset inherits from the next scope out.

Set a limit​

In the operator section, open Quotas. Set the cloud's defaults, a domain's defaults for its projects, or one project's limits.

Setting the cloud's default quotasSetting the cloud's default quotas

A limit below the locked footprint​

A project's stored bytes may include backups held by an Object Lock that nobody can release early. A stored limit below that locked footprint is accepted. The quota view then shows Unmeetable until next to the release schedule. This is the date when enough locked data becomes eligible for deletion to bring usage below the limit. Increase the quota if the project needs to add protection sooner.

The project's view​

Projects with a limit see a Quota section on their overview, and an explanation when they are over: "This project is over its … limit. New resources, new plans and on-demand backups are refused until it is under. Scheduled backups continue." A refused request returns 403 quota_exceeded. The response names the limit, the usage and what the project can do about it.

The ferry_quota_limit_bytes, ferry_quota_in_use_bytes and ferry_quota_locked_bytes metrics carry the same figures per project.