Restoring Data from Snapshots
Snapshot restore procedures in eEKAS should be planned around the protected Ceph resource and the client workload using it. Treat restores as operational changes, especially for block devices and active client access.
Before restoring
- Identify the affected eEKAS/Ceph resource.
- Confirm the required snapshot timestamp.
- Notify connected users or applications before changing live data.
- Consider creating a fresh snapshot of the current state before a destructive rollback.
Restore guidance
- Prefer the smallest restore scope that solves the incident.
- For block-style access, stop or disconnect clients before rolling back to avoid filesystem inconsistency.
- For shared access, coordinate with users so open files and application writes are not lost unexpectedly.
After restore
- Verify the restored data from a client.
- Check application consistency.
- Confirm that scheduled snapshots are still configured as intended.
- Document the selected snapshot and the final result.
This page intentionally describes eEKAS/Ceph snapshot recovery only. Classic filesystem snapshot restore workflows belong in the documentation for the respective euroNAS products.