Backup forum

Hi Steve

I continued attempts in another way.

Logged into admin account, opened Task manager and ended IDrive related task.  Then ran IDrive installer successfully.

Very much appreciated your question (?) re whether is a 'permission' or an 'in-use' issue.   Seems like maybe it was a bit of both. I am keen to learn.

I then rebooted back into admin account and uninstalled using Revo along with a thorough associated cleanup of any leftover artifacts.

I then rebooted into admin account and installed IDrive over the emptiness left by Revo. IDrive system tray icon visible and able from there to access a login interface.

I then rebooted into general user account, opened into IDrive login interface and successfully logged in.

With entire clean install IDrive does not appear to have a connection to previously cloud backed up data from my D (data) drive, so I have 'manually' initiated a data backup of D drive -- currently underway -- appears to be backing up the whole drive -- letting it do that - 3% completed now -- will take a while. 

I found it interesting that in intiating the 'new' backup of D drive, IDrive did not ask for encryption key -- I assume that once set, and unless changed by user, that encryption key holds for all account login events -- is that correct? 

I have not attempted yet, however, I assume the previous backup/s of data from D drive will still be stored and accessible from the IDrive server -- is that correct?

I would like to know what caused the previously installed IDrive corruption -- will probably never know though.

And other insights most welcome.

Very much appreciate your guidance.

Regards

Glad to learn that you got it going.

I can't imagine what caused the IDrive installation to become corrupted. You could spend hours poring over the Windows Event Logs from the time you noticed it broken;  you might find a clue. Alternatively put it down to experience and hope it doesn't happen again