Overview
A snapshot is a point-in-time copy of your Pod's disk that you can use to roll back after a bad change or to clone a Pod. This article explains how to take, manage and restore snapshots from the ALYPOD Console.
Before you begin
- A running or stopped Pod in the ALYPOD Console.
- Enough storage quota/plan headroom for the snapshot.
Snapshots vs backups
- Snapshot: fast, stored alongside your Pod, ideal for short-term rollback before upgrades or risky changes.
- Backup / Storage Box / S3: off-box copies for disaster recovery. Keep these for data you cannot afford to lose.
Best practice: take a snapshot before every major change, and keep off-box backups on a schedule.
Creating a snapshot
- Sign in to account.alypod.com and open the ALYPOD Console.
- Select your Pod and open the Snapshots tab.
- Click Create Snapshot, give it a descriptive name (for example
before-nginx-upgrade) and confirm. - Wait for the status to become Completed. Consistency is best when the Pod is stopped or the filesystem is quiesced.
Restoring a snapshot
- Open the Pod's Snapshots tab.
- Choose the snapshot and click Restore (or Rollback).
- Confirm the warning — current disk contents are replaced.
- The Pod reboots with the snapshot's data restored.
To create a new Pod from a snapshot instead of overwriting:
- Click Deploy Pod and choose From Snapshot.
- Select the snapshot, plan and region, then deploy.
Housekeeping
- Delete old snapshots you no longer need to save storage.
- Name snapshots clearly and note the associated change.
- Automate off-box backups with
restic,borgorrcloneto an S3 bucket.
Troubleshooting
- Problem: snapshot fails to complete. Solution: check free disk space on the Pod and retry; a nearly full disk prevents clean snapshots.
- Problem: data still looks wrong after restore. Solution: you restored an older snapshot than intended — list snapshots and pick the correct timestamp.
Related articles
- [How to reinstall the operating system]
- [Resizing a Pod (upgrading resources)]
- [NVMe Disk Pods explained]
