Current mirror setup

Mirror source:

C:\Sites

Mirror destination:

H:\PrimaryBUs\C_Sites

This is a good first local backup layer because it should include the Astro source, Git history, local Codex notes, source snapshots, DB backup folders, and Storage backup folders.

Important folders to protect

• C:\Sites\my-astro — Astro application source code.
• C:\Sites\my-astro\.git — local Git history.
• C:\Sites\Codex — notes, helper scripts, source snapshots, and backup folders.
• C:\Sites\Codex\supabase_backup_YYYY_MM_DD_HH-mm — database backup folders.
• C:\Sites\Codex\supabase_storage_backup_YYYY_MM_DD_HH-mm — Storage/image backup folders.

Recommended backup layers

1. Git commits: commit important source-code milestones.
2. Source snapshots: create a readable project snapshot after important commits.
3. SyncBackFree mirror: mirror C:\Sites to H:\PrimaryBUs\C_Sites.
4. External/offline copy: periodically copy important backup folders to an external or offline drive.

Suggested SyncBackFree rule

Use a mirror profile from:

C:\Sites

to:

H:\PrimaryBUs\C_Sites

Run it after important project work, especially after:

• source commits,
• new source snapshots,
• Supabase DB backups,
• Supabase Storage backups.

Files that may be bulky but recreateable

These folders can usually be recreated and are not essential if backup size becomes a problem:

• C:\Sites\my-astro\node_modules
• C:\Sites\my-astro\dist
• C:\Sites\my-astro\.astro
• C:\Sites\my-astro\.vercel\output

If space is not a problem, keeping them in the mirror is acceptable.

Mirror warning

A mirror is useful, but it copies deletions and mistakes too. If files are accidentally deleted or corrupted in C:\Sites, the next mirror run may also delete or corrupt them in H:\PrimaryBUs\C_Sites.

For that reason, the mirror should not be the only backup layer. Keep Git commits, snapshots, and occasional external/offline copies.

Secret-file warning

The mirror may include files such as:

C:\Sites\my-astro\.env

That is useful for recovery, but it means the backup drive may contain secrets. Treat H:\PrimaryBUs\C_Sites as sensitive. Do not upload the mirror to cloud storage or share it casually.

After a code backup

Confirm that the mirror contains the latest:

• Git commit history, including .git,
• source snapshot file,
• database backup folder, if one was created,
• Storage backup folder, if one was created.

What this page does not do

• This page does not run SyncBackFree.
• This page does not run Git.
• This page does not back up Supabase DB data.
• This page does not back up Supabase Storage files.
• This page is only a local backup runbook.