Backup & Restore

An AI assistant with write access to your site is only worth using if a bad edit costs you nothing to reverse. Backup & Restore is the safety net underneath every repair MuRu Guard makes -- automatic, not a separate tool you have to remember to run.

It covers more than the Smart AI Assistant: bulk file deletion, Clean Code, Clean Menu XSS, and the rest of the scanner's own one-click cleanup actions all get the same protection.

What it does

• Snapshots before every repair -- taken automatically, server-side, for every AI edit and every cleanup action. There's no setting to forget to turn on.
• SHA-256 verified -- every snapshot is hashed when it's taken and re-verified against that hash before a restore is ever allowed to trust it. A corrupted or tampered snapshot is refused, even with force.
• Per file or per whole request -- an AI turn that edits three files is one transaction. Undo the whole thing in one click, or restore just one of the three.
• Conflict detection -- if a file changed again after the repair it's restoring, the restore stops and asks first instead of silently overwriting it.
• Real diff before you approve -- the same confirmation step where you approve an AI edit shows a line-by-line diff (or a size/hash comparison for binary files), computed locally, never sent anywhere.
• Retention with a Keep override -- snapshots age out automatically on a window you control (days and a maximum count) from Settings > Backup & Restore; pin any specific repair to Keep to exempt it.

How you recover

Every restorable repair shows up in the Protected Repairs list -- a shortcut view inside the Smart AI Assistant panel showing the most recent ones, and the full history under Settings > Backup & Restore. Each entry shows what changed, who approved it, and when. Restoring it is one button: Restore puts the file (or the whole transaction) back exactly as it was, verified against its saved hash first. If something changed again since, a conflict warning appears before anything is overwritten, not after.

Database rows (from Clean Menu XSS, Clean Template Style XSS, and the rogue-asset/defacement cleanup actions) are restored with the exact values they had before -- never a best-effort reconstruction, and never a generic "replay stored SQL" rollback: only the specific, known table-and-action combinations those cleanup actions can produce are ever restorable.

Every snapshot, repair, and restore is also written to the same Protection Log the rest of MuRu Guard uses -- one audit trail, not a second one to check separately.