Snapshots
Snapshots are the fast, local safety net: a point-in-time copy of a domain or the whole server, taken in a moment on the right filesystem, kept close by for quick rollback. They complement backups rather than replace them (backups travel; snapshots stay local).
Backup → Snapshotshttps://YOUR-SERVER-IP:8443/backup/snapshots| Target | Type | Size | Created | Actions |
|---|---|---|---|---|
| 📌 example.com +DB | domain | 1.1 GB | 2h ago | restore · pin · delete |
Instant or standard
Panelica detects the filesystem and picks the fastest method. On Btrfs, snapshots are copy-on-write: near-instant and space-efficient, because they share unchanged blocks with the live data. On other filesystems the panel falls back to a standard rsync copy. A banner at the top tells you which mode is active, and the snapshot list unifies domain and server snapshots on one screen with All / Domain / Server tabs.
A domain snapshot captures one domain's files, plus its database when the domain has one; a server snapshot captures the whole server and is ROOT-only.
Taking, restoring, keeping
Create a snapshot with an optional description. Restore rolls the target back to that point (ROOT-only, and it takes an automatic safety backup first). Pin a snapshot to protect it from automatic cleanup; a pinned snapshot cannot be deleted until unpinned. Delete removes one after confirmation.
Access
Behind the backup license feature (Community and up), with granular create, delete and pin permissions. Domain snapshots follow the roles and permissions chain; the Server tab is limited to ROOT and ADMIN, while creating, restoring and configuring server snapshots, plus retention settings and cleanup, are ROOT-only.