Back up with Duplicati over S3, WebDAV, or SFTP

Duplicati runs on your computer or NAS and controls backup encryption, scheduling, retention, and restores. dosya stores its backup files. Start with a small source folder and restore it before adding the rest of your data.

Steps: prepare backup credentials

1. Choose the destination workspace in dosya. For S3, open Integrations → S3 and copy Bucket, which is your workspace ID.
2. Open Profile → API keys → New API key. Name the key for this backup and choose Full access. Duplicati needs to list, upload, download, and delete backup files when verifying or applying retention.
3. Under Restrictions and expiry, choose Only the ones I pick for Protocols and select S3 gateway, WebDAV, or SFTP to match your destination. Select the destination Workspace and review any expiry or time restrictions.
4. Select Generate key. For WebDAV or SFTP, save the dos_… API key now and use it as the connection password.
5. For S3, expand the saved key’s row and select Enable beside S3 credentials. Save Access key ID and Secret access key before closing the dialog. The secret is shown only when generated.

Your workspace role must permit the selected protocol and the file operations Duplicati needs. Use a different destination folder for each backup job.

Add a backup using S3

In Duplicati, select Add backup → New backup. Name the backup, keep Encryption on AES-256, and set a passphrase. Save it somewhere outside the computer or NAS. dosya cannot recover an encrypted backup without that passphrase.

On the destination step, choose S3 Compatible under Select storage type.

Field	Value
Server	s3.dosya.dev
Use TLS (https)	On
Bucket name	Your workspace ID from Integrations → S3
Folder path	A dedicated path such as duplicati/laptop
Access Key ID	Your generated DOSYA… access key ID
Secret Access Key	The accompanying S3 secret

Keep the default AWS Library. The MinIO Library rejects workspace IDs containing uppercase letters. Use the existing workspace bucket; Duplicati cannot create a new dosya workspace.

Select Test now and confirm that the connection succeeds before continuing. An unused destination should be reported as empty. If Duplicati asks to create a bucket, first recheck the workspace ID and key access.

Use WebDAV instead

Choose WebDAV as the destination type and enter these settings.

Field	Value
Server	api.dosya.dev
Use SSL	On
Path on server	The path from your Integrations → WebDAV address, followed by a dedicated backup folder
Username	Your dosya account email
Password	Your dos_… API key allowing WebDAV

For example, if the app displays https://api.dosya.dev/webdav/mount/ws_example/Personal/, use webdav/mount/ws_example/Personal/duplicati-laptop as Path on server. Keep the workspace ID and label from your own address. Do not paste the whole URL into the server field.

Select Test now. Any new backup folder must be inside the workspace path.

Use SFTP instead

Choose SFTP (SSH) as the destination type.

Field	Value
Server	sftp.dosya.dev
Port	2222
Folder path	/<workspace name>/duplicati-laptop
Username	Your dosya account email
Password	Your dos_… API key allowing SFTP

Use the workspace’s display name in the SFTP path. The server root lists workspaces, so a backup folder must be inside one. If you choose a deeper path, create its parent folders first. Duplicati can create one missing folder level during setup, rather than a whole missing chain.

Select Test now. If you see an SSH host-key warning, follow the SFTP host-key guide before accepting an unexpected key.

Choose sources, schedule, and retention

1. Choose the source files and folders in Duplicati, then set a schedule that fits when the computer or NAS is running.
2. On the options step, leave Remote volume size at 50 MB. Keep it at 64 MB or less. Larger upload requests can be refused, so raising this value can make backups fail.
3. Choose Backup retention, such as Smart backup retention, and leave enough workspace space for the retained versions.
4. Leave remote file lock or S3 Object Lock options off. The dosya gateway does not support S3 Object Lock.
5. Save the job and run it. Wait for Duplicati to finish, then test a restore.

Deleted volumes remain in dosya’s Trash and count toward storage until permanently removed. Automatic removal uses seven days for a Free workspace owner or 30 days for a paid owner. Lowering Duplicati retention may therefore not immediately free dosya storage.

Restore and verify files

In Duplicati, open Restore, choose the backup, select a version, and choose the files to recover. Restore to a new folder for the first test, then open the recovered files and check their contents.

If the original computer is unavailable, install Duplicati on another computer and choose Restore → Direct restore from backup files. Enter the same destination and encryption passphrase. A new dosya key with access to that destination can replace a lost connection credential; it cannot replace the encryption passphrase.

Let Duplicati manage its backup files. Renaming or deleting individual volumes in dosya can prevent restores.

Resolve common problems

• Bucket name cannot have upper case: switch the S3 client back to AWS Library.
• Connection refused or authentication failure: check TLS or SSL, the credential type, the protocol restriction, and workspace permissions. S3 needs its generated access-key pair; WebDAV and SFTP need the dos_… key.
• Uploads fail on large volumes: restore Remote volume size to 50 MB and check the job’s upload errors.
• SFTP folder not found: include the workspace name and create missing parent folders.
• Storage full: check live backups, retained versions, and Trash before changing the job’s retention.

Expected result

Duplicati completes a backup and restores your test files to a separate folder. Open those restored files before relying on the scheduled job.

Related guides

• Connect an S3-compatible client
• Connect with WebDAV
• Connect with SFTP
• Back up a NAS