VPS snapshots versus independent backups
Learn what a VPS snapshot restores, why database consistency matters and which prepared Umbra plans specify a snapshot schedule.
Content revised · English
- Guide type
- Move & recover
- Examples
- Illustrative, environment-specific
- Integration scope
- No remote machine connected
Capture a known useful moment
A snapshot records disk state at a point in time and can help before a package upgrade or major configuration change. Use a name that states the event and capture time. The account workflow does not create a hypervisor snapshot or display real retention capacity.
Check the snapshot schedule on the exact plan
The prepared Umbra 4 plan specifies a weekly snapshot and Umbra 8 specifies daily snapshots. Other tiers need their own expressly confirmed schedule; neither a larger memory allocation nor a separate snapshot option proves inclusion. No hypervisor snapshot or automated backup is created by the configuration and account workflows.
Make database state consistent
A running database can have data in memory or transactions mid-write. Use the database’s supported backup method, a documented quiesce procedure or an application-consistent snapshot design. Do not assume a disk image automatically contains a consistent business record.
Budget storage and retention
Snapshot growth depends on changed data and the storage backend. Keep a retention rule and monitor its cost and capacity. A snapshot on the same host or storage pool may fail alongside the primary service.
Understand the rollback loss
Restoring to an earlier point can interrupt the service and remove later writes, including uploads, orders or messages. Decide which later records must be exported or reconciled. Validate the application after restore and tell the users what changed.
Keep a separate recovery method
Use a tested backup outside the primary failure domain. Versioning and snapshots are not automatically immutable: deletion rights, retention enforcement and separate credentials determine whether ransomware or an administrator can remove them.
Leave with a verifiable result.
- Capture a known useful moment.
- Keep a separate recovery method.
- Keep recovery information and secrets outside public files.
Questions, answered.
Is a snapshot a backup?
A snapshot is a point-in-time disk-state mechanism. If it shares the host, storage or deletion permissions with the primary data, it may fail with them. Use a separately protected backup and test recovery onto another machine.
What data could I lose after a rollback?
Writes made after the captured point may be lost, including uploads, messages and database transactions. Define the acceptable loss, preserve later data where necessary and validate the application after restoring.