@cyberteer Thanks for the how to! Just installed the docker using your guide. I also ran into the "EVS" problem and fixed it using "./idrive -C".

 

I just used your template and let it auto-create the directories.

BTW. there is a small typo in this closing tag <WebUI/> in the template.

 

Just started my backup on iDrive. Thanks again!

Edited May 29, 20242 yr by Redindian

On 5/3/2024 at 7:57 AM, cyberteer said:

Hey @jjross @mraerosmith in regards to the "Unable to find EVS commandline utilities" error you both encountered...  would either of you recall if when you first added the idrive docker if you created a folder/directory under /user/appdata for the idrive docker to use or did you simply let it "auto-create" upon launching the container?

 

I'm really sorry, I can't remember. It's certainly possible I didn't not create the folder as I typically assume it will be created automatically.

On 5/29/2024 at 9:04 PM, jjross said:

I'm really sorry, I can't remember. It's certainly possible I didn't not create the folder as I typically assume it will be created automatically.

 

Thank you for following up.  I suspect that this is the case.  It seems necessary to have created a folder under appdata before executing the docker container.  In some previous instructions it was identified to "touch" the idrivecron.json file as well, again before executing the docker container.   

 

However, it may simply be for this new version of the container that to avoid the EVS error -- that having an "idrive" folder under appdata created before executing the container maybe all that is necessary?!?

On 5/29/2024 at 2:59 PM, Redindian said:

@cyberteer Thanks for the how to! Just installed the docker using your guide. I also ran into the "EVS" problem and fixed it using "./idrive -C".

 

I just used your template and let it auto-create the directories.

BTW. there is a small typo in this closing tag <WebUI/> in the template.

 

Just started my backup on iDrive. Thanks again!

@Redindian Glad you were successful.  Typo has been corrected.

Edited May 31, 20242 yr by cyberteer

Hello All,

Linux & Unraid noob here and I need some guidance. I was able to follow thru the directions to sucessfully connect my Unraid server to my iDrive account using the snorre0815/idrive-docker process. My question is: how do I tell the iDrive-Docker to tell iDriveforLinux which specific file share/folder I want backed up? Can someone point me to or describe a set of instructions I can follow to make this happen? Apologies if my question seems "dumb".

Thanks to All!

11 hours ago, horqua said:

Hello All,

Linux & Unraid noob here and I need some guidance. I was able to follow thru the directions to sucessfully connect my Unraid server to my iDrive account using the snorre0815/idrive-docker process. My question is: how do I tell the iDrive-Docker to tell iDriveforLinux which specific file share/folder I want backed up? Can someone point me to or describe a set of instructions I can follow to make this happen? Apologies if my question seems "dumb".

Thanks to All!

 

Excellent -- glad to see more unRaid users take advantage of the inexpensive backup options offered by iDrive.

 

To configure what files you want to backup, you need to navigate in your browser to the iDrive portal (https://www.idrive.com/idrive/home/), login with your account credentials for iDrive, and then from the left hand panel select "Dashboard" then "Computers".  You'll be presented with a screen showing you the active connected computers to your account.  Select the one which is your unRaid server by clicking it or clicking the details icon.  You'll then be presented with a screen where you can configure the files/folders to backup.

 

I would suggest navigating around within the settings on the iDrive panel.. For familiarity as well as there are options that maybe of benefit or not.

 

Additionally, these iDrive tutorial videos may also be of assistance:

 

https://www.idrive.com/videos#Web

 

 

 

Edited June 20, 20242 yr by cyberteer

I want to start out saying that I am a total noob to Unraid, Linux, and dockers. That being said, by following @cyberteer instructions, I was able to get this working. Only time will tell if it continues to work.

 

And speaking of time, when I deployed this, I had the timezone set incorrectly in Unraid. I fixed that, but the idrive docker still had the wrong time and TZ was set wrong. I'm not sure how to fix that correctly. I have worked around this by adding a TZ variable to the docker, basically overwriting the one passed by Unraid. But I'm sure that there is an actual right way to fix this.

 

Another small issue that matters little if any: the icon for the docker does not show. I set it to the URL provided, but it does not show that icon, just a question mark icon. The URL does show the right icon in a browser. Again, unimportant but curiosity makes me want to know what is going on.

 

Once again, thanks to everyone for their posts and help. I now feel I can actually put real data on my new Unraid server.

Edited August 29, 20241 yr by Cruzerman

On 8/29/2024 at 10:36 AM, Cruzerman said:

I want to start out saying that I am a total noob to Unraid, Linux, and dockers. That being said, by following @cyberteer instructions, I was able to get this working. Only time will tell if it continues to work.

 

And speaking of time, when I deployed this, I had the timezone set incorrectly in Unraid. I fixed that, but the idrive docker still had the wrong time and TZ was set wrong. I'm not sure how to fix that correctly. I have worked around this by adding a TZ variable to the docker, basically overwriting the one passed by Unraid. But I'm sure that there is an actual right way to fix this.

 

Another small issue that matters little if any: the icon for the docker does not show. I set it to the URL provided, but it does not show that icon, just a question mark icon. The URL does show the right icon in a browser. Again, unimportant but curiosity makes me want to know what is going on.

 

Once again, thanks to everyone for their posts and help. I now feel I can actually put real data on my new Unraid server.

@Cruzerman Thank you for the "props".  

 

Timezone (TZ) variable...  if you changed the TZ setting for Unraid any docker apps ALREADY created would not get updated and need to be recreated in order to have their TZ setting updated.

 

Icon issue...  Did you setup the container using the "Template" or "Manual" method?  I did check and the icon image still works -- however, I am not sure for the "Manual" method if you need to include the "https://" part or not (meaning just the part afterwards.

 

and finally, welcome to the Unraid community!

Edited September 5, 20241 yr by cyberteer

I got the icon to work by switching from https to http. As for the TZ, I assumed that was the issue. The TZ was not set properly in Unraid at the time the docker was deployed. I just added a TZ variable to the docker itself. That seems to fix it without me having to redo everything.

 

And the backups are still working great. Very happy with the performance and usability. 

Good day,

 

Unraid says there is an update available for my iDrive docker. Also, iDrive says the server is not running the latest version. However, I am afraid I will break things. Is it safe to update? And what is the best way? Do I update the docker in Unraid, push the update from iDrive, or both?

 

TIA

On 10/9/2024 at 1:50 AM, Cruzerman said:

Good day,

 

Unraid says there is an update available for my iDrive docker. Also, iDrive says the server is not running the latest version. However, I am afraid I will break things. Is it safe to update? And what is the best way? Do I update the docker in Unraid, push the update from iDrive, or both?

 

TIA

If you haven't updated the docker container -- I suggest waiting, there seems to be a flaw somewhere in that after upgrading to v3.5 or beyond -- your container/computer will no longer show as being online in the iDrive webUI dashboard.  For existing container users -- the impact is minimal, your configured backups will continue without issue, however, creating new or adding to existing will be problematic.  

 

For new users wanting to setup iDrive, the current situation with the snorre0815/idrive-docker container will make it nearly impossible to get a backup working.  In the interim, you can switch to the renofischa/idrive container which is frozen at v3.2 -- it works, just don't Check for Update or proceed with doing so as it will upgrade to v3.6 and subsequently break the connection leaving your container/computer showing as offline from the iDrive webUI dashboard.

For anyone experiencing the issue of their iDrive container appearing offline in the iDrive webUI dashboard.  I worked with iDrive Support to help them identify and resolve the issue.  I currently have a custom package that restores the connectivity with the dashboard, but it will be released publicly very soon.  In the meantime avoid iDriveForLinux v3.5 and v3.6 if you can -- however, even though connectivity with the dashboard is broken -- your scheduled backups will continue without issue.

Please note that the latest and tagged 3.6.0 versions of the snorre0815/idrive-docker container have been updated and the computer/container appearing offline in the iDrive dashboard is no longer a problem.

Edited November 21, 20241 yr by cyberteer

Just to say thanks @cyberteer, i had issue with old docker from Taverty (txs to hin anyway, it used to work a long time). I just pull snorre0815/idrive-docker using same patch & config as the old taverty docker, and all works.

For whatever reason, I couldn't get any one method to work, but between a few of these posts, some trial and error, and a lot of chatgpt, here's what worked for me:

 

Step 1: Remove Any Existing iDrive Container & Start Fresh

(warning, this will remove previous settings) 

docker stop idrive

docker rm idrive

docker volume rm idrive

 

Step 2: Create a Persistent Docker Volume

docker volume create idrive

 

Step 3: Run the iDrive Container with Correct Mappings and a Custom Icon

docker run -d --name idrive \

  --restart=always \

  --label "org.unraid.icon=https://static.idriveonlinebackup.com/source/images/favicon.ico" \

  -v idrive:/opt/IDriveForLinux/idriveIt \

  -v /mnt/user:/data:ro \

  -v /etc/localtime:/etc/localtime:ro \

  -e TZ="America/New_York" \

  snorre0815/idrive-docker:latest

 

Step 4: Configure Your iDrive Account

docker exec -it idrive /bin/bash

 

Launch the Interactive Account Setup Menu: Depending on your image version, run one of these commands:

./idrive --account-setting

or

./account_setting.pl

 

Reconfigure Your Account:

• Choose to reconfigure your account.
• Log in using your iDrive credentials and complete any two-factor authentication.
• Confirm the backup location.

 

...I'm a newb, so be warned...Not sure I understand it all...frankly, I have no idea why it works, so no guarantees you won't have problems. I know the appdata backup plugin doesn't like it. But hey, it worked for me.

Edited February 15, 20251 yr by no-one
typo & formatting

7 minutes ago, no-one said:

I know the appdata backup plugin doesn't like it

for the same reason you can't edit it from the edit container page. It has no template since you didn't create it from the add container page. When you click on its icon, only a limited selection of things can be done from the Unraid webUI with that container. For comparison, click on the icon of a container you added from Community Applications.

Hi friends,

 

As many of newcomers to the forum, I am pretty new in Unraid world, trying to do my best to set up my NAS. I have the problem mentioned several times: "Unable to find EVS commandline utilities. Reinstall app or contact support for more information.". I have tried to download again the image and to use the command "./idrive -C" from the console connected to the docker instance terminal, without success, :(. Do you have any other suggestion to try?

 

Unraid version: 7.0.1

 

 

 

Many thanks