Skip to main content
Use approved persistent storage for files that must survive application restarts. In the fixed-volume model, the volume is mounted at /data; files elsewhere in the container can disappear when it is replaced.

​
Allocate storage

When creating or configuring an application, request capacity within the available workspace and cluster allowance. Persistent storage requires a compatible storage agent. The fixed-volume model supports one application replica. Do not assume several replicas can share the same volume or that increasing an application allowance resizes existing storage automatically. Review the operation supported for that service.

​
Understand retention

Retained bytes still consume capacity. A platform administrator reviews permanent purge separately. Confirm the exact resource in its deletion preview.

​
Arrange backups

A retained volume is not a backup. This storage model does not by itself provide replication, automatic cross-node failover or a restore service. Confirm your application’s backup destination, schedule and recovery procedure with its operator.
Export data consistently before a destructive change. Copying a database file while it is being written may not produce a usable backup.