Resolve CodeGuard quota warnings promptly. Prolonged over-quota status can stop backups for the account's sites and databases, leaving the apparent backup service active while no new recovery points are created.
01 Choose a capacity correction
- Record current storage use, allowance and the last successful backup for each important site.
- Identify growth from larger live data, many retained changes or obsolete protected sites.
- Review an appropriate capacity upgrade through us when the data and history are still required.
- If reducing usage, choose documented retention or exclusions only after preserving required recovery points.
- Confirm usage is within the allowed level, then run and verify new file and database backups.
02 Avoid destructive shortcuts
Deleting and re-adding a website can remove its history. Excluding important uploads can reduce size while making recovery incomplete. Choose a correction based on the recovery requirement, not solely the smallest number on the dashboard.
Common questions
Does reducing retention affect only one site?
Check the exact setting and its scope. Account-level retention can apply across multiple websites and databases.
Can I delete old backups safely?
Only after identifying which points the business still needs. Export required copies and verify them before removing their online history.
How do I know backups resumed?
Check for a new completed timestamp and inspect representative contents. A quota warning disappearing is not enough by itself.
Track normal growth and review capacity before major media imports or application changes. Include the current storage, site count and required history in an upgrade request so we can help match the ordered plan to the actual workload. Keep a record of any period during which backups were stopped.