Versioning helps, but resilience also depends on isolated storage and protected credentials.
Steps for Windows
- Choose a separate backup destination not writable by everyday user accounts.
- Keep a second copy or immutable retention layer where available.
- Test restoring a known-clean revision to a separate computer.
- Document how to disconnect compromised endpoints before recovery.
How to verify the result
A known-clean file can be restored from an unaffected destination.
An attacker with full access to all destinations can destroy both live data and backups.
Why this matters
The practical goal is a recoverable Duplicacy revision, not just a successful-looking progress indicator. Keep your source, backup destination, Backup ID and necessary credentials documented. If this workflow changes your retention or storage configuration, verify a restore before applying it to important data.
Frequently asked questions
- How do I plan backups for ransomware recovery?
- Versioning helps, but resilience also depends on isolated storage and protected credentials.
- How can I confirm this worked?
- A known-clean file can be restored from an unaffected destination.
- What should I avoid?
- An attacker with full access to all destinations can destroy both live data and backups.
Primary documentation: Duplicacy Web Edition User Guide · Developer download · Last source review: November 2, 2026. This is an independent editorial checklist, not a claim of hands-on testing.
Set up your Windows backup
Choose the right edition, verify the installer, then test a restore.