Create A Snapshot
- Open the owned storage service and check its snapshot limit and current count.
- Create a snapshot using the module workflow and record its identity and time.
- Confirm the operation result and refreshed snapshot list.
- Keep independent backups; a module snapshot is not an off-host backup strategy.
Choose A Complete Recovery Point
A snapshot bundle can include both file and block components. A file-only snapshot made before an iSCSI volume was introduced is not a complete recovery point for a later file/block account. The documented UI refuses restore of incomplete historical bundles.
Before Restoring
Restoring can revert newer writes. Confirm the intended service and recovery point, arrange the maintenance window, and close protocols/end sessions where required by the supported workflow.
Do not delete another recovery point just to make room for a test. If ownership or completion is uncertain, preserve the operation journal and contact support.
Verify After Restore
Check the result and actual file/block contents from an authorized source after access is reopened. A success message alone does not verify application data integrity. Compare snapshot time with the NAS and WHMCS timezones before diagnosing clock drift.