iDrive backups and MikroTik

RouterOS General
1

I have at least 4 different clients in different locations, all with MikroTik routers, mostly RB750GR3. We have a problem where iDrive cloud backups fail to finish and error out, and it now appears the common thread is MikroTik router firmware released AFTER 6.37x. I have been working with iDrive to fix this issue, assuming it’s with their software, but we now realize the common thread is that all locations with iDrive backups failing are using MikroTik routers, upgraded to newer firmware. Here is a post from these forums in 2017 essentially complaining about the same issues:

I’m having weird idrive backup failures from only some PC’s behind upgraded Microtik routers.
Downgrading to 6.37.5 and backups will start working again.

I’ve opened a ticket with the idrive tech, but I have no idea where to start with troubleshooting this issue.
Here’s example of one network:
Router firmware update 3/9/2017

PC1
Backup 3/8/2017 backup ok
Backup 3/10/2017 backup failed due to “connection issues”

PC2
Backups still running fine 3/15/2017
Backups started failing 3/16/2017

Downgrade to 6.37.5 firmware and backups start working again.

Don’t think a supout.rif is going to help with this.

Any thoughts welcome.<<<

Actually, in our cases, ALL computers performing iDrive backups fail before completing if they are behind MikroTik routers. So this problem has been occurring for at least 3 years. Thoughts and help most welcome!

–AwardB

2

I also found this on the MikroTik forums, no reply but this is the exact problem that is occurring:

I have several clients that use idrive or ibackup cloud backups for some of their data. These backups began failing a while back and I have finally narrowed it down to an update on the Mikrotik routers for these clients. Somewhere around the 6.38 update the backups will only run for a time and the lose connection to the backup cloud. I have no idea what would be causing it and am looking for information that might help.<<<

Thanks

3

Find out where it’s connecting to, what protocol and ports it uses, etc. Then you should be able to watch what exactly happens.