Backup stall and other issues
Several issues were encountered during the setup of iDrive. Currently running on Windows 10.
1. The initial upload obviously takes a long time, even for my 800GB drive. The time remaining counter does not take into account the rollover of days. Or perhaps the estimate of time is so totally wrong.
2. Had several instances where the initial backup totally froze for 10-20 hours displaying the same file being uploaded. CPU usage for iDrive was continuously 75% or more. Tried stopping and restarting without success. Rebooting didn't help. Erased all iDrive files via the web and restarted the backup and the same thing happens. Reinstalled iDrive and the same thing happened but was finally able to stop and restart past the errors and complete a backup. It doesn't stop at the same place each time. A subsequent backup was finally completed without stalling, so hope the problem does not come back. A timeout feature is needed to help get past this type of issue.
3. I have both windows local user and administrator accounts on my computer. Running from the local account let me set up a backup of some files located in the administrator account, but it ran into permission issues during the backup. Starting iDrive under the local account in administrator mode may have helped, but can't remember. I will now just run it while logged into the administrator account.
4. Had a friend at another location do a new install on his computer. During the installation process, he skipped past the point of saving the recovery code. Tried chatting with customer support to see how to get the code, but the support person did not even know what the recovery code was. Even asked how to start the installation over to get the code, but he did not know enough about your product. My friend was going to call support, but don't know the outcome.
5. Haven't tried clone/computer backup to a local drive yet, but after reading the specs for this mode I don't think it has the ability to recover individual files on a time basis. Could be wrong on this issue.
Haven't used iDrive enough at this point to determine if the above issues happen again. If so, I will not use the product.
1/4/23 Update
Continue to have issues with iDrive. Finally got a full backup, but don't trust it. My objective is to run iDrive manually about once a week rather than have continuous operation. Some issues are:
1. The backup log often indicates that some backups files/folders could not be done but it doesn't identify either the files/folders involved or a reason.
2. Manually initiating a backup resulted in missing some files that should be backed. It does go through the process of creating a file list, but apparently doesn't really check for new/old files.
3. Forced it to find other files that needed backup by making just one simple change to the backup selections. For example, to set one file currently in the selection list not to be backed up. It then does a total rescan of files that takes a very long time. But it did find the missing files to be backed up.
4. As mentioned before, the "Estimated Time Left" counter is unreliable.
So at least for now, I have decided not to use iDrive.
