The scripts only deal with the high level things like authentication, configuring, etc (all using the REST API) while the uploads and downloads are deferred to the command line program (the scripts can do upload/download with the REST API as well if hey can't find the binary).If rclone is going to add idrive as a backend, here is one thing that will need to be dealt with

Besides the perl scripts, there is a pre-compiled binary command line utility to deal with high-efficiency data transfers. Their code is a complete mess and I started making a Python replacement before finding rclone for all my other data-movement needs.

I have somewhat studied their perl scripts for idrive-backup (which may also be used for idrive-sync). I am curious if either the idrive-backup or idrive-sync support S3 as well.

- enterprise storage, 2TB is $70/year with discouraged egress, 30-day free trial, definitely supports S3.

Supports WebDAV but is significantly limited.

- for syncing, there is free (5GB) and then higher levels (150GB-1TB, $35-$300/year), much more expensive, presumably since this is designed for high egress unlike the backup one.

- for backup, the free (5GB) and personal levels (5TB, $70/year) don't support WebDAV as mentioned above, higher levels may (although I cannot confirm).

They support S3 as well, see the following resources:Ĭonfusing the matter there seem to be several separate services under similar names:

Rclone idrive