Browse this section

Planning retention and backup storage capacity

Backup capacity depends on the amount of protected data, its rate of change, retention and the backup format. Retaining several recovery points does not always mean storing the same number of full copies, but assumed savings should be checked against real results.

Build a realistic estimate

  • Measure the initial dataset and daily changes, including databases, uploaded files and rapidly growing logs.
  • Define daily, weekly or longer-term retention based on recovery and business requirements.
  • Allow space for temporary operations, full backup cycles, failed jobs and future growth.
  • Review deletion permissions, retention enforcement and access to encryption keys.

Track storage growth and backup success after deployment. If capacity is running low, ask for a reviewed policy or capacity change before deleting recovery points. A longer retention period does not help if backups cannot be restored or the necessary keys are missing.

Was this guide helpful?

Related guides

Defining a backup policy for your service

A useful backup policy starts with the data you need to recover and the loss your business can tolerate. Specify both the recovery point objective, meaning acceptable data loss, and the rec…

RAID, snapshots and backups: what each protects

These mechanisms address different failure situations. RAID or replication can keep data available through some component failures. A snapshot can preserve a point-in-time state. An indepen…

How to request a restore

A restore can overwrite data created after the selected recovery point. State exactly what you need recovered and whether the recovered copy should replace production or be placed in a sepa…

Application-consistent database backups

Copying database files while an application is actively writing may not produce a recoverable backup unless the database and backup method support that process. Choose a method appropriate …

Need help applying this to your service?

Tell us your service reference and what you need to achieve. Never include passwords or private keys in a ticket.

Contact support →
← All knowledgebase topics