Managing VPS Snapshots
Create, restore, and schedule VPS snapshots from the GoZen client area. A full-server backup in seconds.
A snapshot is a point-in-time image of your entire VPS - operating system, files, databases, configurations, everything. It’s faster than a file-level backup because it captures the disk state as a whole.
GoZen Host VPS plans include snapshot functionality through the client area. You don’t need SSH access or any tools installed on your server.
When to Use Snapshots
Use snapshots as a safety net before risky changes:
- Before upgrading your OS or kernel
- Before major application updates (WordPress core, database migrations)
- Before changing server configurations (Nginx, PHP, firewall rules)
- Before installing new software
- As a quick recovery point for development/staging servers
Snapshots are not a backup strategy. They’re stored on the same infrastructure as your VPS. For proper backups, combine snapshots with offsite backups to a separate location.
Creating a Snapshot
- Log into the GoZen client area
- Go to Services → My Services
- Click on your VPS plan
- Find the Snapshots or Backups section in the management panel
- Click Create Snapshot
- Give it a descriptive name (e.g.,
before-nginx-upgrade-2026-04-07) - Click Confirm
The snapshot process takes a few seconds to a few minutes depending on your disk size. Your VPS stays online during the snapshot.
Snapshot Naming Tips
Use descriptive names so you know what state each snapshot represents:
clean-install-ubuntu-2404- fresh OS installbefore-wp-migration- right before migrating a siteworking-lemp-config- known-good server configurationpre-kernel-update-jan-2026- before a specific maintenance task
Restoring a Snapshot
Restoring replaces your entire VPS with the snapshot state. Everything that changed after the snapshot was taken will be lost.
- Go to your VPS management panel in the client area
- Navigate to the Snapshots section
- Find the snapshot you want to restore
- Click Restore
- Confirm the action
Restoring is destructive. Your current VPS state is completely replaced by the snapshot. Any files, database changes, or configurations made after the snapshot was created are permanently lost. Make sure you want to go back to that exact point in time.
The restore process typically takes 1-5 minutes. Your VPS will be offline during the restore and will reboot automatically when it’s done.
Deleting Old Snapshots
Snapshot storage is limited. Delete snapshots you no longer need:
- Go to the Snapshots section
- Find the old snapshot
- Click Delete
Keep your most recent “known good” snapshot and any pre-major-change snapshots. Delete intermediate ones you no longer need.
Snapshots vs Full Backups
| Feature | Snapshot | Full Backup (rsync/Backuply) |
|---|---|---|
| Speed | Seconds to create | Minutes to hours |
| Granularity | Entire server | Individual files/databases |
| Storage location | Same infrastructure | Can be offsite (different datacenter) |
| Restore scope | Full server restore only | Selective file/database restore |
| Survives server failure | Depends on storage setup | Yes (if stored offsite) |
| Best for | Quick rollbacks | Disaster recovery |
Use both. Snapshots for “I’m about to change something and might need to undo it.” Offsite backups for “the datacenter caught fire.”
Best Practices
- Snapshot before, not after. Take the snapshot before you make changes, not after
- Name descriptively. “snapshot-3” tells you nothing in three months
- Don’t hoard. Old snapshots with no clear purpose just consume storage
- Test restores. Do a test restore on a non-production server at least once so you know the process works
- Combine with offsite backups. Snapshots and rsync/Backuply serve different purposes. Use both
What to Do Next
- Backups and Restores - offsite backup strategies for full disaster recovery
- First Boot: Initial Server Setup - secure your VPS from the start
- Monitoring Your Server - watch for issues that might require a rollback
Last updated 07 Apr 2026, 00:00 +0200.