Snapshots capture the complete state of your VPS at a specific moment in time — the operating system, installed software, configurations, and all stored data. They serve as instant restore points that let you recover your server to a known good state if something goes wrong. Whether you are about to install new software, apply updates, or make major configuration changes, taking a snapshot first is a critical safety net.
This guide covers how to create, manage, restore, and delete snapshots on your Data Mammoth VPS.
What Is a Snapshot?
A snapshot is a point-in-time copy of your server's disk. When you create a snapshot, Data Mammoth saves the entire state of your server's storage volume. If you later need to undo changes, recover from a failed update, or roll back a misconfiguration, you can restore the snapshot and your server returns to exactly the state it was in when the snapshot was taken.
Key characteristics of snapshots:
- Instant creation — Snapshots are created almost immediately, regardless of disk size.
- Full disk capture — Everything on the disk is included: OS, applications, data, configurations.
- Independent of the server — Snapshots are stored separately and persist even if the server is stopped or restarted.
- On-demand — Create snapshots whenever you want, as many as your plan allows.
When to Create Snapshots
Create a snapshot before any operation that could potentially disrupt your server:
- Before OS or software updates — Updates occasionally cause compatibility issues. A snapshot lets you roll back.
- Before configuration changes — Modifying web server configs, database settings, or firewall rules. If a change breaks something, restore the snapshot.
- Before deploying new applications — If a deployment goes wrong, you can return to the pre-deployment state.
- After initial server setup — Once your server is configured and working correctly, snapshot it. This gives you a clean starting point to return to.
- Before security experiments — Testing new security configurations, SSH settings, or authentication methods.
- Regular intervals — For important servers, create snapshots on a regular schedule (daily or weekly) in addition to event-driven snapshots.
Creating a Snapshot
The snapshot process begins immediately. Depending on the size of your disk, it may take a few seconds to a few minutes. You can continue using your server while the snapshot is being created.
A confirmation message appears when the snapshot is complete, and it is added to your snapshots list.
Viewing Your Snapshots
Navigate to the Snapshots tab on your server's detail page to see all existing snapshots. Each snapshot entry shows:
- Name — The descriptive name you gave it.
- Date created — When the snapshot was taken.
- Size — The storage space used by the snapshot.
- Status — Whether the snapshot is ready, in progress, or has an issue.
Restoring a Snapshot
Restoring a snapshot reverts your server's disk to the exact state captured in the snapshot. Everything that changed after the snapshot was taken — new files, configuration changes, software installations, data modifications — is lost.
Steps to Restore
The server will restart during the restoration process. Depending on the snapshot size, the process may take a few minutes. Once complete, your server will be running in the exact state it was in when the snapshot was taken.
Important Considerations
- Data loss warning. Any data created or modified after the snapshot was taken is permanently lost during restoration. If you need to save current data before restoring, create a new snapshot or download important files via SSH first.
- Server downtime. The server is unavailable during the restoration process. Plan restorations during low-traffic periods if possible.
- IP address. Your server's IP address (e.g.,
203.0.113.10) does not change during a snapshot restoration. - Running services. All services restart after restoration. Verify that your applications are running correctly after the process completes.
Deleting a Snapshot
Snapshots consume storage space. Delete old or unnecessary snapshots to free up space and keep your list manageable.
Warning: Deleted snapshots cannot be recovered. Make sure you do not need the snapshot before deleting it.
Snapshot Best Practices
Naming Conventions
Use consistent, descriptive names that include:
- Purpose — What the snapshot captures or precedes (e.g., "Pre-update," "Clean-install").
- Date — When it was taken.
- Version — Application or OS version at the time.
Snapshot Rotation
Do not accumulate unlimited snapshots. Establish a rotation policy:
- Keep the most recent 3-5 snapshots.
- Delete older snapshots once newer ones are verified.
- Always keep a "known good" baseline snapshot (your initial clean setup).
Snapshots Are Not Full Backups
Snapshots are stored within the same infrastructure as your server. For true disaster recovery, complement snapshots with:
- Automated backup add-ons — Store backups in a separate location. See Available VPS Add-ons.
- Off-site backups — Download critical data to your local machine or a separate storage server.
Test Your Restores
Periodically test that your snapshots work by restoring one to a test server. A backup you have never tested is a backup you cannot trust.
Snapshots vs. Automated Backups
| Feature | Snapshots | Automated Backups |
|---|---|---|
| Trigger | On-demand (manual) | Scheduled (automatic) |
| Frequency | Whenever you choose | Daily, weekly, or custom |
| Management | You manage creation and deletion | Managed with retention policies |
| Cost | May be included in plan | Available as an add-on |
| Use case | Before specific changes | Ongoing data protection |
What to Do Next
- How to Reinstall Your VPS Operating System — Start fresh if a snapshot restore is not enough.
- Available VPS Add-ons — Add automated backups for continuous protection.
- Optimizing VPS Performance — Keep your server running efficiently.
- Using Rescue Mode on Your VPS — Access your server's disk when it will not boot normally.