Restore
Restore
Restore file to captured state
Every captured change carries its SHA-256-addressed content in BLOB_STORE. Restoring writes that content back to the original path — current file gets backed up to <path>.drift_restore_backup_<epoch> before overwrite.
What will change
Preview -- nothing has been written yet.
| Target file | /var/www/vhosts/3dshawn.com/site1/README.md |
| Site | DriftSense self-monitor on local |
| Kind | local |
| Captured at | 2026-07-11 23:36:38 |
| Captured SHA | b7628512be54e31528f04fb5609b36a5dd7f874c21da952d4949ec8e19f4a531 |
Current state on disk
Live check just now. If SHAs match, the restore is a no-op.
| File present | yes |
| Size | 7987 bytes |
| Current SHA | b7628512be54 |
| Same as captured? | yes -- no-op |
Recent restores of this file
This file has been restored before — check whether you want to duplicate that action or pick a different captured moment.
| Status | Source SHA | By | Error | When |
|---|---|---|---|---|
| success | b7628512be54 | operator | Jul 11 23:36 | |
| success | 3fdb8f6a2875 | operator | Jul 11 23:36 |
Confirm restore
Backs current content to <target>.drift_restore_backup_<epoch>, writes the captured content, verifies SHA post-write.