Volumes

When to use volumes

Volumes are ideal for file storage, cached assets, and data that should survive restarts. You can attach volumes to apps, workers, or databases to keep data persistent.

Volume lifecycle

• Create a volume from the project settings or service detail panel.
• Attach it to a service and choose a mount path.
• Increase its storage reservation as your planned usage grows.

Reservations and disk usage

Reserved storage is an increase-only capacity commitment used by Nouva when scheduling managed volumes on your server. Increasing it does not resize a filesystem or run an agent operation. Docker local volumes are not quota-enforced, so applications can write beyond the reservation. Monitor real usage and Docker storage headroom to avoid filling the host disk.

Snapshots and backups

Use snapshots to capture file based workloads or to stage a recovered volume before you swap it onto a service. PostgreSQL point in time recovery uses pgBackRest, not filesystem snapshots. A staged restore reserves capacity equal to its target volume, but the reservation does not limit filesystem writes.

Best practices

• Mount volumes to clear, dedicated paths like /data or /var/lib/app.
• Keep backups of critical volumes before major releases.
• Practice the restore workflow before swapping a recovered volume into production.