Give a growing file collection room to breathe.

1. Separate the collection from the filesystem.

Write down both the application’s reported usage and the space used on the underlying filesystem. They answer different questions. A member’s quota says how much that account may store under the application’s rules. It does not necessarily describe everything using the VPS disk.

Nextcloud’s documentation, for example, separates user quotas from metadata, older versions and deleted items; some application data also lives in the database. Do not turn a quota total into a disk-capacity forecast without checking those other categories. Retention behavior also depends on configuration and version. Nextcloud 33 storage quota documentation.

Use the same units throughout your worksheet. If one tool reports decimal GB and another reports GiB, label the difference instead of treating the numbers as directly interchangeable.

2. Give each kind of storage a line.

Keep originals, versions, deleted items, previews and temporary work separate. Add the operating system, application, database and logs. If an external folder is mounted, record which storage system actually holds it; a familiar folder name does not prove the bytes are on the VPS.

For every line, record its present size, the reason it grows, the retention decision and the person who can change that decision. “Versions” needs an application setting or documented policy. “Temporary” needs a cleanup owner and a completion condition. A forgotten export archive is still real disk usage even after its original purpose has ended.

Do not delete caches or application directories because their names sound disposable. Check the chosen application’s supported maintenance procedure first.

3. Work through a hypothetical collection.

Imagine a small historical-interest group keeping scanned newsletters and event photographs. The following figures are planning assumptions in decimal GB, not measurements or a capacity promise. They reserve four months of growth before the next decision.

The 10 GB export allowance cannot hold a second complete 96 GB collection. A full export would need a different target or a revised budget. That is a useful finding to make before scheduling the export.

4. Budget the recovery copy separately.

A second directory on the same VPS does not resolve the loss of that VPS. Record the independent destination, access owner, retention rule and restore location on a separate worksheet. Budget its capacity from the actual backup method and retention policy; do not assume compression or deduplication will achieve a particular saving.

A complete application recovery set can require more than user files. Nextcloud lists its configuration, data, database, themes and custom applications where present. Its backup procedure also considers consistency while data changes. Follow the documentation for the installed version rather than copying a live directory and calling the result complete. Nextcloud backup components and consistency.

Keep access to the independent copy available to a second authorized maintainer without putting credentials in the budget sheet.

5. Decide what happens before space runs out.

Choose a review threshold tied to the next planned activity. For the hypothetical collection, the group might review when its remaining free space can no longer accommodate the next agreed import plus temporary processing and its operating reserve. That rule is more useful than waiting for an arbitrary percentage to turn red.

When growth exceeds the worksheet, identify the category first. More accepted originals may justify more storage. Unexpected versions, failed cleanup or runaway logs need investigation. Changing retention affects what people can recover, so obtain the agreed approval and verify the independent copy before permanently removing material. Avoid using emergency deletion as the collection’s normal operating plan.

6. Check the worksheet against a real cycle.

After an authorized import or editing cycle, compare observed growth with each allowance. Confirm that a user near their quota still receives a useful application error and that the host retains operating room. Review the largest categories without exposing private filenames in shared reports.

If application usage looks modest but disk space falls quickly, inspect versions, deleted-item retention, temporary uploads, exports and logs. If a backup grows unexpectedly, compare its selected paths and retention changes. If space is already critically low, pause further imports and avoid producing another large local archive while investigating. Record what changed and update the budget; do not hide the difference inside a bigger unexplained allowance.

7. Keep capacity and usefulness together.

Storage planning cannot decide which records the group should keep. Agree that separately, including who can approve deletion and how members learn about a retention change. Also record whether the files remain readable: an intact collection of obsolete formats may still need an export or conversion plan.

Take the worksheet to the VPS configurator when you know the resource totals you need. Then plan portable exports and a restore drill. This guide gives a budgeting method; it does not guarantee that a particular disk size will accommodate an unknown collection.