Skip to main content

​
Identify the data location

Connect through SSH and inspect the application’s configured data path and mounts. Determine whether files were stored in a managed app release directory, the workspace root disk, or a separate volume.

​
Recover carefully

Preserve the current disk and error evidence. Choose a retained app release for a code/configuration failure, a root-disk snapshot for a system filesystem failure, or an application backup for data loss. Check recovery boundaries first. A snapshot is not a backup of persistent volumes, and creating a new snapshot replaces the workspace’s previous checkpoint. Do not create one reflexively when trying to recover the old one.

​
Prevent recurrence

Store mutable files on a declared persistent volume, configure an application-consistent backup, and test restoring it. Verify persistence by creating a record, redeploying, and reading the same record afterward.