3-Tier Auto-Backup Daily Snapshots, Drive Mirror & Emergency Recovery
ReviewAudited by ClawScan on May 1, 2026.
Overview
This is a coherent local backup guide, but users should review the PowerShell script they create and be careful with scheduled backups and mirror restore commands.
Before installing, decide exactly which workspace folders should be backed up, where backups will be stored, and who can access those backup locations. Review the PowerShell script before scheduling it, be cautious with robocopy /MIR restore commands, and remember that backups may contain sensitive files from your workspace.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A backup process may keep running in the background every day and copy or delete backup files according to the script configuration.
The skill instructs the user to create a persistent scheduled task that runs a PowerShell backup daily. This is disclosed and aligned with automated backups, but it continues running until removed.
Register-ScheduledTask -TaskName "AI Workspace Backup" -Action $action -Trigger $trigger
Only schedule a script you have reviewed, use correct paths, run it with limited privileges where possible, and keep instructions for disabling the scheduled task.
The safety of the actual scheduled backup depends on the script the user creates or obtains outside the distributed skill artifacts.
The operational backup script is not included in the artifacts, while the instructions rely on it. This is not hidden execution, but users must supply and review the script themselves.
The `daily-backup.ps1` PowerShell script is described in README.md. Create it manually in your workspace using the template provided. ClawHub does not distribute `.ps1` files directly.
Do not run or schedule any generated or third-party PowerShell script until you inspect it, understand each command, and verify the paths and retention behavior.
If the source or destination path is wrong, a restore or mirror operation could overwrite or delete workspace files.
The documented restore command uses robocopy /MIR, which mirrors the source to the destination and can remove destination files that are not present in the backup.
robocopy "D:\WorkspaceBackup" "{WORKSPACE}" /MIRTest restore commands on a temporary folder first, confirm source and destination paths, and keep at least one separate snapshot before running mirror-style restore operations.