Support article
Snapshots and Backups on Your VPS: How and When to Use Them
Learn to use snapshots and backups on your VPS: differences, when to make them, how to restore them and best practices to not lose data.
Introduction
Backups are the life insurance of any server. If something fails, gets deleted or compromised, a good backup lets you go back in minutes. Snapshots are a special type of copy, so fast it’s like a photograph of the server.
In this article you’ll see what they are, when to use each, and how to configure them so you never lose your data.
Snapshot vs backup: what’s the difference
Although they seem the same, there are important differences:
| Aspect | Snapshot | Backup |
|---|---|---|
| What it saves | The complete server state at an instant | Selected or complete files and/or database |
| Speed | Instantaneous (seconds) | Slower (minutes or hours) |
| Restoration | Returns the entire server to the snapshot state | Restores specific files or databases |
| Independence | Depends on the original server | Independent (can be stored elsewhere) |
| What it’s for | Before risky changes | For disaster recovery |
Summary: the snapshot is a quick photo of the entire server, ideal before a dangerous change. The backup is a more complete and independent copy, ideal for disaster recovery.
[Imagen sugerida: comparative diagram of snapshot vs backup]
The ideal is to combine both: snapshots for everyday changes and backups for long-term protection.
When to make a snapshot
Make a snapshot before:
- Updating the operating system.
- Installing or uninstalling a control panel.
- Making important configuration changes.
- Updating WordPress, plugins or themes.
- Installing new software.
If something goes wrong, you restore the snapshot and return to the previous state in seconds.
At miHosting you can create snapshots from your VPS panel with one click.
When to make a backup
Make a backup periodically (daily or weekly) to protect against:
- Hardware failure.
- Accidental data deletion.
- Server attack or hack.
- Complete server loss.
The backup should be stored somewhere other than the server, so that if the server disappears, the backup stays safe.
How to make a snapshot
From your VPS management panel:
- Log in to the provider panel where you manage your VPS.
- Find the Snapshots or Create snapshot option.
- Give it a descriptive name, for example
before-updating-wordpress. - Confirm. In a few seconds it will be created.
[Imagen sugerida: screenshot of the create snapshot button in the VPS panel]
Snapshots take up space. Don’t accumulate too many: create the one you need, use it and delete it when no longer needed.
How to restore a snapshot
If you need to go back:
- Go to Snapshots in the VPS panel.
- Select the snapshot you want to restore.
- Click Restore or Revert.
- Confirm.
The server returns to the exact state of the snapshot moment. All subsequent changes are lost.
⚠️ Restoring a snapshot deletes everything done afterwards. Use it only when you’re sure you want to go back.
How to configure automatic backups
To avoid depending on remembering manually, it’s best to automate. There are several options:
Option 1: Control panel backups
Most panels (CyberPanel, cPanel, DirectAdmin) have their own backup system:
- Log in to the panel.
- Find the Backups section.
- Configure the frequency (daily, weekly).
- Indicate where to save them (preferably on another server or external storage).
Option 2: Command-line backup
You can use tools like rsync or borg to copy files to another server:
rsync -avz /var/www/ user@other-server:/backups/
And for the database:
mysqldump -u root -p wordpress > /backups/wordpress.sql
Automate it with cron to run every night.
Option 3: Managed backup service
If you don’t want to handle it, hire a managed backup service. At miHosting we can configure and maintain backups of your VPS for you.
[Imagen sugerida: diagram of the three automatic backup options]
Recommended backup strategy
A good strategy combines several layers:
- Snapshot before changes → for immediate recovery.
- Daily backup of files and database → for data loss.
- Weekly backup on another server or location → for complete disasters.
- 30-day retention → to be able to go back to any point in the last month.
Useful tips
- Make the snapshot before, not after. If you wait until something fails, it’s too late.
- Store backups elsewhere. A backup on the same server doesn’t help if the server disappears.
- Test restoration. A backup you’ve never restored may not work when you need it.
- Name snapshots clearly.
before-update-nginx-2026-07-11is better thansnapshot1. - Check space. Snapshots and backups take up disk space. Clean up old ones.
Common problems
I don’t have space for more snapshots
Snapshots take up disk space. Delete old ones you no longer need or expand the VPS disk.
The backup takes a long time
It depends on data size and connection speed. For large servers, make incremental backups (only what changed) instead of full ones every time.
I restored a snapshot and lost data
That’s normal behavior: restoring a snapshot returns the server to the snapshot state, deleting what came after. That’s why it’s important to also have recent backups.
The automatic backup stopped working
Check that cron is still active, that there’s disk space, and that the destination server credentials are still valid.
I don’t know if my backup works
Test it. Restore it in a test environment and verify the data is complete and correct.
Frequently asked questions
Are snapshot and backup the same?
No. The snapshot is a quick photo of the server, ideal before changes. The backup is a more complete and independent copy, for disaster recovery.
Is it worth having both?
Yes. They’re complementary: the snapshot for immediate recovery and the backup for long-term protection.
How much space do snapshots take?
It depends on the server state and subsequent changes. Panels usually indicate the size taken by each snapshot.
Where should I store backups?
Preferably on another server or storage different from the VPS, so that if the VPS fails, the backup stays safe.
How often should I make backups?
For production websites, daily is recommended. For more critical projects (online stores), it may be worth every few hours for the database.
Protect your VPS with backups
Snapshots and backups are your safety net. The snapshot saves you from risky changes; the backup saves you from disasters. Combining both, automating them and testing restoration is the best way to sleep peacefully knowing your data is safe.
If you don’t want to handle configuring and maintaining backups, at miHosting we offer managed VPS with managed backups: daily copies, retention and restoration by our technicians. Open a ticket from your client panel and we’ll help.