#Expandrive vs duplicati how to#

Slack, discourse, CI, docs, whole nine yards. I do appreciate the overkill approach to development though. In reality – it’s a mishmash of features, and looks more like a playground for developers and their egos than a user-centric product it’s needlessly over-engineered, while being permanently not ready.

On paper it is a superset of duplicacy – both in functionality, flexibility, and complexity. I wanted to like kopia, I played with it. With Kopia you have to write scripts to make it work. There goes your “advantage of active development”.Īnother tidbit: support for filesystem snapshots on macOS. In comparison, when the same was suggested to Duplicacy – it was added pretty promptly: This partly offsets the ‘no stable version’. Unless I misunderstood the Duplicacy state, there’s another advantage to Kopia.

does not support mounting the backup history as volume.

most advanced settings are not in UI, and some UI areas require a lot of rework (exclusion patters, restore workflow).

outstanding suppprt where the developer responds quickly and fixes issues users face even while using the products in most weird and unsupported scenarios (I’m one of those users).

has stable version and exists for a long time.

out of the box support for excluding known transient files (such as TimeMachine exclusion by xattr) - this drastically reduces the need to write custom exclusion patters.

super fast exclusion patters, including regex.

rather simple to make it work with immutable storage.

support for asymmetric RSA encryption (different backup and restore keys).

tons of cloud destinations supported, including google drive.

erasure coding making possible use of ureliable storage (hard drives) as backup destination a.

this is convenient if you have multi clients and copy one from another

backup configuration is stored on the client.

Generally, not very friendly support forum - this is subjective of course.

At which point will he throw in the towel? The dude works at google and develops it on the weekends.

unclear future and support model - most questions and requests are answered by “here is source, pull requests are welcome”.the chunks store will be gc and reorganised to decrease server storage usage Can be workaround with rclone destination but this adds a layer of complexity). very limited support for cloud destinations (no *Drive type services.no stable version yet - so not suitable for production.

#Expandrive vs duplicati how to#

rather complex multilevel datastore structure that if corrupted not clear how to recover.My suggestion to implement that on the forums was met with complete silence. does not support extended attributes driven exclusions (for example to exclude all Files skipped by Time Machine on a mac).support to run server side component to facilitate ACLs.It’s nice and frequently requested feature on duplicacy forums. ability to mount backup history as a virtual drive.backup configuration is stored on the destination.