Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Backups

Storage quota planning: set limits without surprising a growing workload

Published August 2026 · 2 min read · Updated 2026-09-05

Storage quotas are boundaries that keep one account, user, dataset, or project from consuming all available space. Good quota planning starts with expected working data plus growth, temporary operations, logs/caches, mail/uploads, and a clear response when the soft/hard boundary is approached.

Measure working set and growth

Record current used bytes and inodes/file count, then observe weekly/monthly growth and burst operations such as imports, deployments, database dumps, image generation, or mailbox growth.

Quota should not be equal to today’s use; leave normal operating headroom.

Separate live data from backups/temp files

Do not store independent backups inside the same quota unless the product intentionally counts them there. Temporary exports or database dumps can double storage during maintenance and need planned workspace.

Set log/cache retention so quota is not consumed by data nobody intends to keep.

Use warnings before hard failure

Alert at a percentage or runway threshold early enough to clean up or upgrade. Hard quota failures can interrupt uploads, mail delivery, database writes, package updates, and application sessions.

Expose quota status to the operator/customer where the platform supports it.

Review after application changes

A new plugin, media workflow, mailbox usage, or retention policy can change growth materially. Reforecast and resize after workload changes; a first quota event is not a reason to remove limits.

  • Track bytes and inodes.
  • Include maintenance headroom.
  • Alert well before hard limit.
  • Reforecast when workload changes.

Next step

Measure current use, growth, temporary files and operational headroom before setting quotas, then alert before the limit turns a normal write into an outage.

Explore DotMoose backup storage

Keep reading

Related guides.

Backup capacity planning: estimate storage from change rate and retention

Model source size, daily change, compression, deduplication, retention and growth so backup storage is sized from the workload instead of one full-copy estimate.

Read the guide

Backup encryption basics: protect copies at rest and in transit

Choose where backup data is encrypted, how keys are stored and recovered, and how restore operators gain access without putting the only key beside the backup.

Read the guide

Backup recovery drills: prove the restore process before an outage

Run isolated recovery tests, measure restore time, verify application state and record missing dependencies so the backup plan is based on tested recovery.

Read the guide

More backups guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move