Tunlr.Sync Guide: Set Up Continuous Backup in Minutes
Overview
Tunlr.Sync is a lightweight file-sync tool that continuously backs up selected folders to a remote location (cloud or self-hosted). This guide walks through quick setup, key settings, and verification so you have continuous backups running in minutes.
Quick prerequisites
- Tunlr.Sync installed on the source machine (Windows, macOS, or Linux).
- Remote destination configured: cloud storage credentials (S3/compatible) or an SSH/SFTP/self-hosted Tunlr node.
- Stable internet connection for remote backups.
- Basic terminal or GUI familiarity.
5-minute setup (step-by-step)
- Install Tunlr.Sync
- macOS/Linux: download the package or use the provided installer; on Linux you can typically install via the provided .deb/.rpm or extract the tarball.
- Windows: run the installer and follow prompts.
- Create a profile
- Open Tunlr.Sync (GUI) or run:
bash
tunlr-sync init –profile default
- Open Tunlr.Sync (GUI) or run:
- Select folders to back up
- GUI: Add folders using “Add Source”.
- CLI:
bash
tunlr-sync add-source –profile default /path/to/folder
- Configure destination
- For S3-compatible:
bash
tunlr-sync set-dest –profile default s3://bucket-name –access-key YOUR_KEY –secret-key YOURSECRET –region us-east-1 - For SSH/SFTP:
bash
tunlr-sync set-dest –profile default sftp://user@host:/backup/path
- For S3-compatible:
- Enable continuous mode
- GUI: Toggle “Continuous Sync” or “Watch for changes”.
- CLI:
bash
tunlr-sync enable-watch –profile default
- Start the service
- GUI: Click “Start”.
- CLI (run as background service):
bash
tunlr-sync start –profile default –daemon - Optionally register as system service:
bash
tunlr-sync install-service –profile default
- Verify initial backup
- Check logs:
bash
tunlr-sync status –profile default tunlr-sync tail-logs –profile default - Confirm files appear at remote destination.
- Check logs:
Key configuration options to consider
- Exclusions: add file patterns or folders to ignore (e.g., node_modules, .git).
- Versioning: keep previous versions of changed files for a set retention.
- Bandwidth limits: throttle upload speed during work hours.
- Encryption: enable client-side encryption before sending to remote.
- Conflict resolution: choose last-writer-wins or keep both copies with timestamps.
Best practices
- Start with a small test folder to confirm behavior.
- Enable versioning if accidental deletions are a concern.
- Use client-side encryption for sensitive data.
- Monitor logs for the first 24–48 hours after setup.
- Periodically test restores to verify backups are usable.
Troubleshooting (common issues)
- Permission errors: ensure Tunlr.Sync runs with access to source folders and destination credentials are correct.
- Large initial sync slow: run initial backup on a wired connection or use a physical seed if supported.
- Missing files: check exclusion patterns and file filters.
- Service not starting: inspect systemd/service logs or use the built-in log viewer.
If you want, I can generate the exact CLI commands for your OS, create an exclusion list for typical projects, or write a systemd service file for automatic startup.
Leave a Reply