1Use snapshots before a system change
VPSDZ includes five manual snapshot slots per server. A snapshot gives you a restore point before changing software, configuration or the operating-system image. Create it from the Snapshots tab and wait for the provider operation to complete before relying on it.
2Understand what restoration changes
Restoring a snapshot replaces the current system state with the selected restore point. Changes made after that point may be lost. The console requires the exact hostname before a restore or reinstall to make the target explicit. Review the snapshot date, image and name before confirming.
3Keep a separate copy of important data
Snapshots are not included automatic offsite backups. Maintain an independent copy of critical application data under your own backup policy. Choose a backup destination, retention schedule and access controls that suit the data you store. A server snapshot should not be the only copy of information you cannot replace.
4Check application consistency
A database or application may need its own export, flush or backup procedure to produce a useful recovery copy. Follow the application documentation and check what your restore process requires. A disk-level restore point and an application-aware backup solve different recovery needs.
5Test recovery before you need it
A backup is useful when you can restore the required data. Periodically test a recovery procedure in an appropriate environment and check that the recovered application works. Name snapshots clearly, remove older points when you need another slot and keep separate records of your own backup arrangements.