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/affiliate.3dshawn.com/_billing_worker.pl
SiteAffSoft (affiliate.3dshawn.com) on local
Kindlocal
Captured at2026-07-01 13:48:17
Captured SHA4f795cec52e80307bc99d2d879b8832947c6b17ff5bb8e15732ea14e0a6012dd
Current state on disk
Live check just now. If SHAs match, the restore is a no-op.
File presentyes
Size4778 bytes
Current SHA4f795cec52e8
Same as captured?yes -- no-op
Preflight compile-check ?
perl compiles cleanly — restore is safe to proceed.
Confirm restore
Backs current content to <target>.drift_restore_backup_<epoch>, writes the captured content, verifies SHA post-write.
Cancel Logged to RESTORE_LOG regardless of outcome.