Scoped credentials limit the damage from accidental exposure of cloud backup secrets.
Steps for Windows
- Create a storage-specific credential with needed read and write permissions.
- Avoid reusing a primary administrator cloud account.
- Store the secret only in Duplicacy's intended configuration fields.
- Rotate exposed credentials and perform a new backup and restore test.
How to verify the result
The backup works using the restricted credential rather than global admin access.
Revoking an active key can break scheduled jobs until configuration is updated.
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 manage cloud access keys for duplicacy?
- Scoped credentials limit the damage from accidental exposure of cloud backup secrets.
- How can I confirm this worked?
- The backup works using the restricted credential rather than global admin access.
- What should I avoid?
- Revoking an active key can break scheduled jobs until configuration is updated.
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.