rclone VS kopia

rclone: a command-line program to manage files on cloud storage.

Synchronise buckets with Sclone or Rclone

Says that Apple doesn't provide a multi platform API. It doesn't provide any official supported way to access iCloud from Windows, Linux.

There's a ticket covering everything you might ever want to know:

https://github.com/rclone/rclone/issues/1778

seconding rsync and syncthing.

the server could expose an smb or nfs share, the client could mount it, and then sync to that mount.

rsync over ssh also works, if you do not want to run smb/nfs.

this is also a cool tool https://rclone.org/

rclone [1] to dropbox. works since years without problems

[1] https://rclone.org/

rclone provides a special pCloud config option, which makes the setup straight forward. rclone can encrypt the data it uploads with its own encryption but not with the pCloud encryption. Therefore it can only upload data to the unencrypted pCloud folders, not to the Crypto Folder.

The arkclone project impliments rclone in ArkOS to achieve cloud saves. Not yet built in to ArkOS yet, and not a lot of recent traction on the pull request to get it added, but it can be installed manually.

I think Kopia would be great for your use case

https://kopia.io/

It has a great system to snapshot files but only store data if it's changed. I use it in an environment where I can't use something like zfs to snapshot data because I don't have the ability to make decisions about what filesystem we're using. It's been amazing, love it so much!

Thanks for the tip on Kopia. Setting it up now, looks perfect.

https://github.com/kopia/kopia

Kopia - GitHub

I've been happy with: https://kopia.io/

Fairly easy to configure, does snapshots to S3 and has a icon in my tray I can watch :)

Btw, kopia is one fine backup tool. Apparently borgbackup is good too.

Kopia is great, though it's worth noting for folks on Linux: non-UTF-8 paths aren't stored correctly [1] and xattrs aren't stored [2]. While most folks probably won't care about the former, the latter can could cause issues (eg. losing SELinux labels makes it difficult to restore a backup of the root filesystem on distros that use SELinux).

[1] https://github.com/kopia/kopia/issues/1764

[2] https://github.com/kopia/kopia/issues/544

I think Kopia [1] is on its way to be that. I am sticking to Restic for now but it seems like the strongest contender.

[1]: https://github.com/kopia/kopia

I used their trial for a bit to test it out with Vorta [1] in a container. Vorta (and Borg) seemed to work fine, until I wanted to restore an archive and I noticed that my recent snapshots were completely empty. Probably because of a misconfiguration on my end though. But it made me look elsewhere. For me backups should be a fire, test and forget solution.

Recently I made the switch to Kopia [2] which seems to have feature parity with Borg (and Restic [3]). It also has a web UI which is way easier to work with than Vorta. And I can easily view, extract and restore individual files or folders from there. This gave me way more confidence about this solution. The only thing I really miss is that I cannot chose different targets for different paths. For instance, with Borg I was able to backup a partial of my Docker appdata to an external source. And I haven't found a way to do this with Kopia. Besides that I'm pretty happy with this solution and I would recommend it.

1. https://vorta.borgbase.com/

2. https://kopia.io/

3. https://restic.net/

There's a few. Off the top of my head

https://github.com/kopia/kopia