A snapshot captures disk state at a point in time. It can help recover from a configuration change, but you should confirm snapshot availability, retention and restore procedures for your selected service.
Before a risky change
Make a recoverable copy and check that you know how to restore it. Record what the copy contains, when it was made and whether restoring overwrites newer data. Do not assume a fixed rollback duration.
Snapshots and independent backups
A copy stored alongside the primary server may share its failure risks. Ask where a backup is stored and what retention applies. Paid backup options appear in the configurator; do not assume that an option guarantees storage in another country or an unlimited retention period.
For a self-managed encrypted copy, see the Restic backup guide. Keep the repository credentials somewhere independent of the source server.
Application consistency
A disk snapshot is not automatically an application-consistent database backup. Use the database backup procedure appropriate to your software and verify a restore. Test the data and application together before relying on a backup for recovery.