Protect your data firstKeep a current off-server backup before reinstalling, updating, changing firewall rules, or running an application installer.
On this page
Record what persists
Identify named volumes, bind mounts, database storage, uploaded files, and environment settings. A container image is not a backup of persistent data. Preserve the deployment definition and required secrets outside the VPS.
Plan the update
- Read the vendor's release notes and supported upgrade path.
- Back up files and take an application-consistent database backup.
- Test the new version with a copy of data in a separate environment.
- Schedule a maintenance window when migrations or downtime are expected.
- Verify login, key workflows, logs, and backups after the update.
What not to do
Do not use volume removal or indiscriminate pruning as an update procedure. An old image alone cannot reverse a database migration. Never assume changing an image tag is reversible after the application has changed stored data.