Idrive e2 raising prices 24%

Off Topic
1

i just got an email from idrive.

"To accommodate increased infrastructure costs and continue providing you with reliable and scalable cloud storage, we will be adjusting the prices for your Yearly (5 TB) plan. The plan rates will increase from $100 to $247.5 at renewal. The storage overuse charges over your plan will increase from $0.004/GB/Month to $0.005/GB/Month"

note: idrive e2 gives a 50% discount for the first year.
so the first year is $100.00, and would expect the second year to be $200.00
that is a 23.75% increase, year to year.

now, the price is $247.50, which is $4.125/TB/month

2

Is that for idriveE2? Glad I didn't stay with them then (I left because the transfer speed was very erratic and unreliable over time).

3

yes. thanks, i edited the title of the topic to reflect that.

i actually have a few 5TB accounts.
for now, i will continue to stay with idrive for another year.

on the whole, i have found them to be reliable and their tech support very responsive.
tho, the uploads speeds seem to have slowed down over time.

however, if idrive jacks up the price like that again, i will switch back to wasabi.
wasabi have much, much better support for s3, such as user/bucket polices and session tokens.
and transfer speeds and latency are much better.

4

Depends on your use case, I guess.
I moved some data to Jottacloud and some to pCloud. Both are much faster and their fast speeds are much more consistent than iDriveE2 was. E2 started well but download speeds dropped to unacceptable levels. I moved buckets to a different location, same issue, started well then dropped.

5

yeah, that right.

in the past, i keep recent backups in wasabi. has fast downloads, low latency.
great for disaster recovery using veeam instant recovery.
and kept older backups in amazon s3 deep glacier.

now, maybe i need to reconsider that again...

6

If you don't mind the 90 retention. My backup works as append only so I can stand it but the principle of it bothers me to no end!

1 Like
7

hi @jwink3101, yes, each time i post about wasabi, you chime in about that ;wink
if i remember, you use B2?

for those who do not know about the wasabi mandatory 90 day retention period, it could quickly become an expensive nightmare.

tho, in my case, it is just 30 days.
"Timed Deleted Storage (applicable for deleted storage < 30 days)"

yes, i have taken look at the python code.
very nice

in my case, with wasabi, the backups are basically append only.
veeam backup files - with each backup, it is a single file, that once created never changes.
and .7z files, a single file that once created never changes.
makes pruning very easy using rclone filters.

8

Thank you for saying that. I didn't realize I had become such a broken record. I will back off on that. I do use B2 amongst others but I also only store ~1Tb on S3-like systems

Thank you. Honestly, if I had the time and Go knowledge, I'd rather implement a "versioning" backend for rclone. Combine it with some kind of file cache and you can ignore my tool. I am more happy with the approach over the tool itself. I love that my backups can be manually interrogated and restored.

1 Like