I understand the concept of a minimally viable product, especially in SW, but not showing what failed to backup is a huge oversight. May I suggest that "soon" is changed to "by Oct 1st". The information is obviously within the system - it just needs to be reported.
eengr on "how to see which files failed to backup?"
roma on "Synology package 2-step verification not working"
I installed iDrive v2.03.16 on my Synology DS412+. 2-Step verification is not working. I can login iDrive without entering a number and without checking the checkmark at the login page. I can log in just with administrator credentials username/password and add, modify and delete backup schedules. I do have 2-step verification enabled on my Syno.
IDrive on "iDrive backup consistently fails: "Connection Failed. Unable to connect to the server. Try late"
We request you to send across the application logs to our tier-2 team who can look into the issue you are facing. The error report can be sent by using the "Send Error Report" option from the IDrive application by clicking on Username on top right corner of the IDrive application. Our tier-2 team would review the application logs and respond with the troubleshooting steps.
For faster seeding, you can also make use of our IDrive Express service. IDrive allows for quick backup and retrieval of data via a temporary storage device. This is a FREE service, available once a year for Pro Personal users and thrice yearly for Pro Business users (either backup or retrieval). This service includes free return shipping and is available in the USA, Canada, Germany, France, Italy, Australia and the UK. More information on IDrive Express is available here: https://www.idrive.com/idrive-express
IDrive on "how to see which files failed to backup?"
@eengr We have forwarded your feedback to our development team.
IDrive on "Synology package 2-step verification not working"
We request you to let us know your account username/email address so that we can escalate this to our technical team and advise you on the further course of action.
Also, you may send us a request through: https://www.idrive.com/support.htm
jer73 on "Scheduled backups stopped since 10 Sept 2015 & ERROR: auth failed on module ibackup"
Just checking my Synology Idrive Logs, to find out that I have no successful daily backups any more since 10 Sept.
Manually starting a Backup, yields the following error message:
@ERROR: auth failed on module ibackup from 5469626A.cm-12-2b.dynamic.ziggo.nl (84.105.98.***): unauthorized user
idevs error: error starting client-server protocol (code 5) at main.c(3020) [sender=1.0.2.8]
Hey Idrive - what's up? I would like to have a RELIABLE backup for my NAS. I was using Idrive 2.3.15 on a DS214play, just upgraded to v2.3.16 but no improvement. I am logging in as Admin.
miketdd on "Background processes running in OS X client"
The follow tasks are constantly running in the background of my machine, even if i close drive:
IDriveDaemon
Drive Monitor
IDWebManagement
IDWifiManager
I can't force quit these because they just automatically start up, even if Drive is NOT running.
These are eating up (albiet) small amounts of my RAM and CPU and would like to know how to turn these processes off when Idrive is closed.
IDrive on "Scheduled backups stopped since 10 Sept 2015 & ERROR: auth failed on module ibackup"
For immediate assistance, please get in touch with us on live chat: https://www.idrive.com/support
IDrive on "Background processes running in OS X client"
Please get in touch with us on live chat from the following link: https://www.idrive.com/support
jer73 on "Scheduled backups stopped since 10 Sept 2015 & ERROR: auth failed on module ibackup"
This was indeed more a helpdesk than a forum issue. Issue was resolved by helpdesk in a few minutes (log off - log on). My learning point: important to regularly check the logs if scheduled backups have run. I did not get any warning/error e-mail, while Notify was 'on error'.
IDrive on "Scheduled backups stopped since 10 Sept 2015 & ERROR: auth failed on module ibackup"
You can receive an alert in case your scheduled backup fails. Click on 'Preferences' > 'General' tab from the IDrive tray. Select the 'Alert me if the scheduled backup fails for 7 days' check box to receive a desktop alert in case your backup has not taken place. By default, it is set to seven days.
Robin Dean on "The Whole "Retrying" Thing is Getting Pretty Old."
... and what's worse, I'm a new customer.
The fact that a backup has to start over whenever there's a hiccup? Not cool. I'm backing up an entire computer.
Why not just pick things up from where the error occurred, starting at the file (or event) which caused the error?
Starting from the very beginning is flat out ridiculous.
Pikappa on "QNAP iDrive app password not accepted since upgrade"
Hi, just updated qnap to firmware 4.2 and the admin password is not working .... Cancyou help me?
IDrive on "The Whole "Retrying" Thing is Getting Pretty Old."
For immediate assistance, please get in touch with us on live chat from the following link: https://www.idrive.com/support
IDrive on "QNAP iDrive app password not accepted since upgrade"
@pikappa, Let us know if it is the NAS password or the IDrive password that is not being accepted. Please let us know your account username or the email address that you have registered with us so that our Tier 2 technical team can review the issue and provide you with troubleshooting steps. You can also place a support request from the following link: https://www.idrive.com/support
dstuffle on "The Whole "Retrying" Thing is Getting Pretty Old."
And the every response from IDrive being "please get in touch with us on live chat" instead of a actual reply and / or steps to take gets old.
Why have a forum if that's all you ever say?
bobbee on "iDrive Backup Engine Stopped."
After receiving notice of IDrive update, I complied and updated IDrive one day ago. The IDrive engine has not started since that "new" install. In fact, IDrive doesn't even show up in the "services.msc" list any longer. So, the suggestions for a "work-around fix" that involve "services.msc" are no longer applicable for me because Idrive is no longer in the "services.msc" list. This is DEFINITELY a bug that needs fixin'
bobbee on "iDrive Backup Engine Stopped."
PaulH on "iDrive Backup Engine Stopped."
I had this problem a few weeks ago (ticket ID00720765. ) and the change in properties I was provided with worked fine
1. Go into Service Control Manager[run=>services.msc] 2. Right click on IDriveService and choose properties.
3. In the dialog which appears, change the startup type to "Automatic Delayed Start .
Also, right click on IDriveService and choose properties, select Recovery tab and set First Failure, Second Failure, Subsequent Failure to Restart the service and then restart the machine. Check if the service starts automatically on restart of the machine.
ALl has been well until I installed the latest version 6.4.0.8 and then late yesterday I saw a message saying idrive service had crashed.
Now the idrive icon in the tray says "idrive backup engine has been stopped. Restart the backup engine to continue the operation". There is no idrive service in the services engine. looks like the fix broke something??
IDrive on "iDrive Backup Engine Stopped."
@PaulH We have re-opened the ticket ID00720765. Our Tier 2 technical support team will get in touch with you soon.