Most people’s backup plan is one external drive in a drawer and a vague intention to plug it in. Kopia replaces that with encrypted, deduplicated snapshots from every laptop, desktop, and server you own, sent to storage you control.

Why Kopia Suits a House Full of Devices
Kopia is an open-source backup tool written in Go. It ships as a command-line program and as KopiaUI, a desktop app for Windows, macOS, and Linux. Every platform uses the same repository format, so a snapshot taken on a Windows laptop can be restored on a Linux server without conversion tools or compatibility headaches.
Encryption happens on your machine, before a single byte leaves it. The default cipher is AES-256-GCM, with ChaCha20-Poly1305 available as an alternative, and the storage provider only ever sees opaque blobs. That changes how you can think about storage. You no longer need to trust the company hosting your bucket, which means the cheapest S3-compatible provider is as safe a choice as the most expensive one.
Deduplication is what makes a shared repository sensible rather than wasteful. Kopia splits files into chunks and stores each unique chunk once, so a photo library copied across a desktop and a laptop costs you the storage of one copy. Compression is applied on top, and after the first snapshot, later runs only upload what changed. A household of five devices does not cost five times as much to store.
The supported backends cover nearly every setup. Kopia can write to a local disk, an SFTP server, WebDAV, S3-compatible services such as Backblaze B2 and Wasabi, Google Cloud Storage, and Azure Blob. It can also reach anything rclone can talk to. Self-hosters have an obvious extra target: the export folder from a Paperless-ngx install is exactly the kind of irreplaceable data a nightly snapshot should cover.
Create the Repository and Connect Each Machine
Start by installing Kopia on the first machine. Homebrew handles macOS, official package repositories exist for Debian-based and RPM-based Linux distributions, and Windows has a standard installer. If you prefer a graphical interface, grab KopiaUI instead, since it bundles the command-line engine and walks you through the same steps below with a setup wizard.
The repository gets created once, from whichever device you set up first. For an S3-compatible bucket, the command is kopia repository create s3, followed by flags for your bucket name, endpoint, access key, and secret key. Kopia then prompts for a repository password. Make it a long passphrase and store it in a password manager, plus a printed copy somewhere physically safe, because the encryption key derives from it and nothing else.

Every other device connects to that same repository instead of creating a new one. Run kopia repository connect s3 with the same bucket details and the same password, or choose the same provider in the KopiaUI wizard. Kopia identifies each client as username@hostname, so snapshots stay grouped per machine even though the underlying chunks are shared. Give each computer a distinct hostname before you connect, or two devices will blur into one identity.
Now take a first snapshot with kopia snapshot create and the folder path, for example your Documents directory. The initial run is slow because everything is new, but the follow-ups finish quickly. Before you automate anything, set retention with kopia policy set –global and flags such as –keep-daily 7, –keep-weekly 4, and –keep-monthly 12. Add ignore rules with –add-ignore for bulky, regenerable folders like node_modules and cache directories, which would otherwise burn storage on files you can rebuild in minutes.
Scheduling depends on the device. KopiaUI runs snapshots on a timer while the app is open, and you can set the interval through –snapshot-interval in a policy. Headless machines are better served by a systemd timer, a cron job, or Windows Task Scheduler calling kopia snapshot create. If you would rather not hand your bucket credentials to every device, Kopia also offers a repository server: run kopia server start on one trusted machine, add accounts with kopia server user add, and clients authenticate to the server instead of the storage itself. A lost laptop then exposes one revocable login, not the keys to your entire backup bucket.





