Backup Operations

Manual, scheduled, or real-time — choose how you want to protect your data

Manual Backup

Want to back up right now? One click.

Select a backup source in the sidebar

Click the Backup Now button

Watch the progress bar — you'll see real-time stats as it runs

Set your schedule once. Ginkgo handles the rest.

Select a source and open Settings

Pick a frequency under Schedule

Save. Ginkgo runs on that schedule from now on.

Schedule Type	What It Does
Manual	You trigger backups yourself. No automation.
Hourly	Runs once per hour, every hour
Daily	Runs once per day at your chosen time
Weekly	Runs on your chosen day and time each week
Monthly	Runs on your chosen day and time each month

Turn on Watch mode and Ginkgo monitors your files in real time. Save a file? It gets backed up immediately.

💡 Watch mode is ideal for active projects — code, writing, design work. For general use, Daily scheduling is usually enough.

Not everything needs backing up. Set exclusion rules for temp files, caches, and build artifacts.

Open the source settings and find Exclude Patterns

Add patterns like *.tmp, node_modules, .git, build/

Save. Those files are skipped from now on.

💡 Patterns support wildcards: *.tmp matches any .tmp file. Directory names match the entire tree.

Ginkgo compresses backup data automatically. Pick the algorithm that suits your files best.

Algorithm	Best For
zstd (Recommended)	General purpose. Best balance of speed and compression ratio.
s2	Large files where speed matters most.
deflate	Legacy compatibility.
none	Already-compressed files (JPEG, MP4, ZIP). Avoids double-compression overhead.

💡 When in doubt, use zstd. It's the right choice for nearly every scenario.