How to Use Keriver Disk Sync for One-Way and Two-Way BackupsKeriver Disk Sync is a file synchronization and backup utility designed to keep folders identical across drives, network locations, and removable media. It supports flexible mirroring and backup strategies, including one-way (source → target) and two-way (bi-directional) sync. This guide explains how to plan, configure, and maintain both one-way and two-way backups with Keriver Disk Sync, plus tips to avoid data loss and improve performance.
Before you start: plan your backup strategy
- Identify what you need to protect: documents, photos, project folders, or entire drives.
- Choose a destination: external drive, NAS, cloud-mounted folder, or another local folder.
- Decide frequency: real-time, scheduled daily, weekly, or manual.
- Determine retention/versioning needs: do you need previous versions or just mirroring?
- Consider bandwidth and power: large syncs benefit from wired networks and AC power for laptops.
One-way backup: overview and when to use it
One-way backup copies changes from a source folder to a target folder without propagating changes back to the source. It’s ideal when the source is the authoritative location (e.g., a primary workstation, server, or camera import folder). Use cases:
- Routine backups of a PC to an external drive.
- Server-to-NAS replication.
- Offsite copies for disaster recovery.
Benefits: simpler conflict handling, safer against accidental deletions at the destination (if configured as mirror/overwrite), and easier to schedule.
Two-way sync: overview and when to use it
Two-way sync keeps two locations synchronized in both directions so changes in either place are reflected in the other. Use cases:
- Working across multiple devices where edits can happen on any device.
- Collaborative folders shared among team members.
- Syncing between desktop and laptop where both are actively updated.
Two-way sync requires conflict resolution rules because the same file may be edited in two places between syncs.
Installing and preparing Keriver Disk Sync
- Download and install Keriver Disk Sync from the official site or trusted distributor.
- Launch the app and allow any required permissions for file system access.
- Ensure both source and destination locations are accessible and have sufficient free space.
- (Optional) Create a test folder with sample files to practice settings before running on critical data.
Creating a one-way sync job
- Open Keriver Disk Sync and choose “New Task” or “New Sync.”
- Select the Source folder (the authoritative location).
- Select the Destination folder (where files will be copied).
- Choose the sync mode — pick a one-way mode such as “Copy” or “Mirror/Update”:
- Copy: copies new/changed files but may not delete at destination.
- Mirror/Update: makes destination match source (adds, updates, and can remove files).
- Set filters if you want to include/exclude file types or subfolders (e.g., exclude *.tmp, node_modules).
- Configure file conflict and deletion behavior:
- If mirroring, decide whether deletions on the source should delete at the destination.
- Optionally enable a recycle/trash feature so deleted files are moved to a safe folder first.
- Schedule the task: run manually, at logon, on file change (real-time), or on a timer.
- Enable logging and email notifications if available and needed.
- Run a dry-run or simulation (if Keriver supports it) to preview actions without modifying files.
- Start the task and verify the destination contains the expected files.
Example settings for a safe daily backup:
- Mode: One-way Mirror
- Deletion: Enabled but move-deleted-to-recycle
- Schedule: Daily at 02:00
- Logging: Detailed
Creating a two-way sync job
- Open Keriver Disk Sync and create “New Task.”
- Select Folder A and Folder B as the two endpoints.
- Choose a two-way or bidirectional mode (often called “Two-way Sync” or “Mirror Both Ways”).
- Configure conflict rules:
- Prefer Newer: keep file with the newest modification time.
- Prefer Specific Location: prefer changes from Folder A or B.
- Keep Both: rename one copy to preserve both versions (e.g., filename (conflict – device).ext).
- Set exclusion/inclusion filters as needed.
- Decide how to handle deletions:
- Propagate deletions (if you want deletes to mirror).
- Soft-delete: move deleted items to a local archive to allow recovery.
- Choose schedule: continuous (watch mode), frequent interval, or manual. Watch mode is useful for two-way sync but can increase CPU/IO.
- Test on non-critical data to ensure conflict behavior matches expectations.
- Run the task and check for conflict reports; resolve any issues found.
Practical two-way conflict settings:
- Rule: Prefer Newer
- On exact timestamp match: Keep Both (rename)
- Deletions: Soft-delete to archive
Conflict detection and resolution best practices
- Prefer a timestamp-based rule but verify clocks are synchronized across devices (use NTP).
- Use “Keep Both” if you cannot risk overwriting edits. Renaming preserves both versions for manual reconciliation.
- Keep detailed logs and enable an archive/recycle option so you can restore deleted or overwritten files.
- For multi-user folders, consider coordinating edits or using a versioned file service (Git, cloud storage with versioning) for active collaboration.
Scheduling and performance tips
- Use incremental sync modes to copy only changed files (saves time and bandwidth).
- For large initial syncs, run the task locally or during off-hours to avoid disrupting users.
- For network locations, prefer wired Gigabit connections or schedule during low-use windows.
- Limit simultaneous file transfers to avoid saturating I/O; many sync tools let you set parallel thread counts.
- Exclude large transient folders (e.g., caches, build outputs) to reduce unnecessary IO.
Verifying and testing backups
- After initial run, compare folder sizes and file counts; spot-check file contents.
- Periodically perform a full restore test: copy files back to a test location and open several files to verify integrity.
- Review logs weekly for errors or skipped files.
- Keep at least one independent, offline backup (air-gapped disk or offsite storage) to protect against ransomware or catastrophic failure.
Advanced features and automation
- Use command-line options or scripting (if Keriver offers them) to integrate tasks with system automation or scheduled jobs.
- Combine with compression/encryption for offsite storage: create encrypted archives before sending to cloud targets.
- Use filters and file masks to tailor tasks for specific projects or file types.
- If Keriver supports pre/post scripts, run checksum verification, notifications, or cleanup tasks automatically.
Troubleshooting common issues
- Permission errors: run the app with appropriate privileges or fix folder permissions.
- Skipped files due to locks: schedule during idle times or enable retry-on-failure options.
- Time mismatch causing conflicts: synchronize clocks (NTP).
- Slow transfers: reduce parallel file count, use wired networks, or exclude large files for separate transfer.
- Deleted files unintentionally propagated: restore from archive/recycle and change deletion settings to soft-delete.
Safety checklist before relying on sync
- Have a tested recovery plan and at least one offline backup.
- Keep logs and enable notifications for failures.
- Test conflict rules with non-critical data.
- Ensure destination has excess free space (at least 20% recommended).
- Regularly verify backups with random file restores.
Example scenarios
- Personal laptop → external drive (one-way mirror nightly, soft-delete enabled).
- Desktop ↔ Laptop (two-way, prefer newer, keep both on exact ties, continuous watch).
- Office server → NAS (one-way scheduled hourly, detailed logging, notifications).
Summary
One-way sync with Keriver Disk Sync is best when you have a single authoritative source and want predictable backups; two-way sync is for active bi-directional workflows but requires clear conflict rules and verification. Plan, test, and use soft-delete/archiving to protect against accidental data loss. Regularly verify restores and maintain at least one independent offline backup.
If you want, tell me which operating system and target locations you’ll use (external drive, NAS, cloud) and I’ll give step-by-step instructions specific to your setup.
Leave a Reply