Is a VPS snapshot the same as an independent backup?
A snapshot records a point-in-time state according to the platform’s implementation. It is not automatically an independent copy with separate retention, credentials or failure protection. Review what is captured and what events could make that recovery point unavailable.
Instructions
1. Identify the snapshot’s exact scope
Confirm included disks, whether memory is captured, consistency level, retention and deletion behaviour. Separately attached storage, external databases and object stores may not be covered by a VPS snapshot.
2. Check independence and access protection
Determine whether recovery data shares the same storage, account and deletion permissions as the live service. The recovery design should reflect the events you need to survive, such as data corruption, mistaken deletion, account compromise or a regional outage.
3. Verify the recovery point through the supported workflow
In Britixo’s Snapshots area, inspect the selected snapshot details and completed status. A listed or requested snapshot is not enough: use an approved isolated restore test to establish that the required application and data can actually be recovered.
Check the result
- The recovery scope includes every required data source and dependency.
- A tested recovery point remains accessible under the failure scenario the plan is intended to address.
Troubleshooting
- The snapshot disappears when the service is deleted
- The recovery point may be tied to the service lifecycle; confirm retention before cancellation or deletion.
- The snapshot restores the OS but not application data
- Identify excluded volumes or external dependencies and correct the recovery design.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.