cyberteer

Could I kindly ask if you would use this to create one for the Terramaster F2-424? (2-Bay NAS)?

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.

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.

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.

@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!

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

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

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?!?

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?

Thank you @jjross for your input. Two reports is certainly more than coincidence. As mentioned, I don't seem to be able to replicate the issue on my Unraid installation and I wasn't able to replicate it on Ubuntu VM running docker that I'd setup to see if I could. I will raise the issue with the container builder as perhaps there is something there.

I appreciate the props, but still doesn't explain why the container failed initially. I suspect that if you make a change to the docker template (change volume path to backup something else or add another volume path) that the container gets rebuilt and you'll be back to having to run the update again. I'm glad to know you are up and running. iDrive really is the least expensive backup option that I have found. Simply put $10/year for 500GB is a fantastic deal. In addition, I am quite pleased with the speed at which backups have executed. Good luck!

@mraerosmith can you try executing: ./idrive -C and force it to update even if it says it is the same version.

I am on Unraid version 6.12.10, If you are older, it might be attributable to an older version of docker. What do you see when you execute: docker version from an Unraid terminal window?

Yes, I am sorry as I am at a loss as to why that is happening. Something is corrupt or corrupting the container, as I again pulled the image on a different computer and it works as expected.