IDriveforMac is a user-friendly, secure and reliable application that performs automated online backup of your files and folders.
The application safeguards your critical data in case of a system crash. The graphical interface is coupled with powerful scheduling and logging features.
Incremental backups - only modified portions of files are backed up, thereby conserving bandwidth
Data compression during transmission that lead to quick backups
Enhanced security with 128-bit SSL encryption on data transfers
Network or Mapped Drive backup support
Automatic
What's New
Version 2.0.0: Release notes were unavailable when this listing was updated.
In this version, deleting large files from the remote server by selecting the checkbox then clicking the delete icon doesn't work. They have to be deleted one at a time by selecting the file, control-clicking and selecting "Delete".
Offers more than twice the free space allotted by Dropbox. However I don't need this extra space anyway, and I find the Dropbox interface more enjoyable. However, you can use both at the same time!
Overall it seems like a very decent app, though I would like to be sure I can trust the developer before sending them my most sensitive data.
I guess nothing beats a good, high quality fast external hard drive to back up one's data. hmmm?
Personally, I wouldn't trust my valuable or sensitive data to some storage facility in God-knows-where.
But, to each his/her own.
If your house burns down, odds are your Mac and your external go up in flames.
There's a lot of value in off-site backups. And as others have said, there's multiple ways to encrypt your data before you send it anywhere
I have some portable HDs encrypted using TrueCrpy that I shuttle between home and office. Hard to beat the bandwidth of the bus!
If you are mistrusting of the provider and think they can / will read your stuff, then encrypt the data before you copy it there. MacFuse is your friend here.
Some handy instructions (hopefully the links are OK):
http://www.hutsby.net/2011/06/howto-using-encfs-with-dropbox-on-osx.html
http://www.hutsby.net/2011/05/getting-started-with-truecrypt-and-osx.html
This app needs work. It very often freezes (it doesn't crash though): the spinning beach ball of death, and you can't do anything. This is not that relevevant if it is going on in the background since it always comes back somewhen. It's just annoying when you want to cancel an automatic backup (not enough bandwidth at the moment for example), you have to wait for iDrive to be responsive again.
Another problem in my opinion is the memory usage. Right now, with *no* backup going on, it uses 150MB RAM ("real memory" column in activity monitor) which is quite a lot for a background daemon...
Otherwise it's ok, and still a better (or "less worse") interface than the one from Mozy (where you can't even get rid of the menu bar item - mine is already cluttered, I really don't need another item there.).
I have been wanting offsite backup, and investigated several options. Finally I selected iDrive, mostly because their software is vastly better than that of any competitor. Yet I have one serious reservation. Since iDrive only permits archived backups, and since it limits you to 150 GB, sooner or later I'm going to use up my quota, and I haven't a clue what's going to happen then. I e-mailed their support asking about this, and never received an answer, which suggests to me that they don't have a clue either. So if by the time I hit my limit they haven't come up with a solution to this problem, I'll probably just walk away from this service and look for another one. And I bet this is going to be the reaction of a large part of their customer base. So it is really in their own best interest to face up to the fact they have a problem on their hands. There are two ways of fixing it, both of which I would find acceptable: a.) give us the option of simple mirrored backup with no archiving, or b.) use the Time Machine "first in first out" scheme, whereby old archives are automatically cleaned out to preserve space for new backups. Let's hope the developers wake up and smell the coffee over this one. (Better security protection would be very welcome too).
Also, anybody with a fairly large body of data that needs to be backed up should be aware that the initial upload is going to take a long time (mine took over five days). If you aren't very cool about using the bandwidth throttle you're internet performance is going to take a massive hit.
Just signed up for this service - in respect of archived backups and space taken up; they do actually seem to ignore these. they refer to them as snapshots in the case of their Mac service; this from the FAQ section -:
"The available daily Snapshots have been set to 10 (This may change without notice). The additional storage requirements for Snapshots have no impact on your account quota usage."
Once 150GB is filled, you can simply add an additional account and control from the same software. Honestly, I don't see the issue with providing 300Gb for double the cost, but, they don't seem to offer that right now and simply allow you to buy as many accounts with 150GB as you want....
Still persevering with this, though it's trying my patience a little. yes, there's kind of a sync option available now - though it seems to be a manual process (a per-time comparison of online and offline folders) that is far from intuitive, and not the same as mirroring. The multiple machine set-up seems flakey too. I want to like this service, and they are updating features fairly regularly, but it's just not right yet...
I (and many other people) want simple, automatic mirroring of folders. This can't be that hard.
This is yet another backup-to-cloud client in the same vein as Mozy, SpiderOak, and JungleDisk. A 2GB account is free, while a whopping 150 GB can be had for $49.50/yr.
Unfortunately, the Mac client serious lags behind the Windows client. As pointed out by numerous reviewers, there is no data encryption available for Mac, leaving your files unencrypted on the servers. While the web site claims versioning, this is only available for Windows; a poor substitute "Snapshots" is available for Mac, which makes you go through the last ten backups searching for a previous version. In my experience, Snapshots were unreliable as well as tedious (think Time Machine, only very limited). If I want a previous version of a file, I want to see what versions are available, not have to dig.
Unlike SpiderOak and JungleDisk, the same storage cannot be shared between a Mac and a PC client. A web interface is available.
Support from the developer is responsive but unhelpful. "Encryption is being consider in the future and we will notify our customers when it is available".
I suspect this is quite a nice program on the PC, but it has a long way to go for us Mac users.
iDrive is incompatible with OS X package files as well as legacy Mac OS files that contain resource forks.
A common file that you would want to backup: QUICKEN DATA
After recovering your Quicken Mac 2007 data file, you will quickly realize that the package file has become a folder and the contents of the package file (now a folder) are all corrupt and unrecoverable!
Mozy, as slow and unreliable as it is, at least doesn't corrupt the contents of the package file - but it does change the package file into a folder. You have to use a utility like FileMatey (Google it) it convert the recovered folder back into a package, and then it works. With iDrive, this is NOT the case.
I don't want to SPAM too much in this comment, but I want to post my iDrive tech support transcript to show that they confirm the issue, so here it is (sorry it's long):
Trevor:
I'm attempting to recover a backed up Quicken file for Mac and it appears that iDrive has corrupted all of my backed up Quicken files...
Call accepted by operator Technical Support. Currently in room: Technical Support.
Technical Support:
Hello Trevor, you are chatting with Karthik.
Technical Support:
How are you today?
Trevor:
ok
Trevor:
are you familiar with Mac OS X files?
Trevor:
specifically a Mac OS X package file?
Technical Support:
Yes. Let me see what I can do Trevor.
Could you please let me know if you are receiving any errors?
Trevor:
no errors. The file/package is being backed up by iDrive on an automated schedule. When I recover the file/package, it is recovered as a FOLDER instead of a package file and the contents are corrupt. The backup is useless... your FAQ states that customers should ZIP the pagage files before backup - this defeats the automated purpose of iDrive
Trevor:
Any way I can get the package file restored?
Technical Support:
Trevor, let me check this issue from our end and will let you know what could be done.
Technical Support:
Please give me few minutes.
Trevor:
here is a link to your FAQ - http://www.idrive.com/online-backup-mac-faq.htm#12sub
Technical Support:
Trevor, could you please let me know if this package file in your account is being displayed as a folder or not?
Trevor:
its being displayed as a folder in iDrive.
Trevor:
and it is also a folder when recovered from iDrive back to my Mac
Trevor:
it is a package file originally on the Mac
Trevor:
I'm reading the FAQ - it states that iDrive doesn't backup files with resource forks and it also states that it may fail with package files...
Trevor:
Bottom line, iDrive is NOT compatible with Mac OS X. You should not be selling it to Mac users because you are giving them a false sense of security.
Technical Support:
Trevor, IDrive for Mac application is compatible with Mac OS X. We have tested this and there are many customers using without issues.
Currently, could you please send us the log files from the application? Use the Send Error Report feature. You can find the Send Error Report feature when you right click on the IDrive Tray Icon and then click Send Error Report. Alternatively, you can find it under the Help menu, after you login into IDrive application.
Trevor:
there are no error reports. I don't feel that you are completely understanding what I am talking about.
Trevor:
the customers that are using it are unaware that they have been mislead. they are "using it without issues" because they don't know that they are losing data
Trevor:
where do you want me to send the error report?
Trevor:
what is the trouble ticket number?
Technical Support:
Trevor, the error report is a consolidated log that lets us know if there are any issues with the functionality of the application. This helps us in determining the issue effectively.
Trevor, ignore the ticket# field for now. Fill in your details and submit.
Technical Support:
Trevor, we have not had any such reports. We have many customers who are backing up packages without issues. They are able to restore them as well. In this case we need to analyze what could have happened.
Trevor:
report sent successfully
Technical Support:
Ok. Let me check. Please give me 2 minutes.
Trevor:
how can you say this when it is listed in your FAQ?
Trevor:
you're lying to me!?
Trevor:
The IDrive for Mac application has not backed up some files inside the bundle / file package. Why?
This could be because the files are Mac OS X files or hidden or the file names contain special characters. We recommend that you compress (zip) the entire bundle / file package and try backup.
Trevor:
Does IDrive for Mac backup files that contain extended attribute i.e. resource fork data?
No. IDrive for Mac does not backup files that contain extended attributes i.e. resource fork data.
Trevor:
these two FAQ items make iDrive incompatible with Mac OS X.
Technical Support:
Trevor, could you please let us know the name of this package file?
Trevor:
Main Accounts
Trevor:
located in users/trevor/documents/quicken data/main accounts
Trevor:
main accounts is the package file
Trevor:
FYI the files inside of the package file are also being corrupted - most likely because they contain resource fork information.
Technical Support:
Trevor, we need to consult our development team on this. We will get back to you via email with an update at the earliest.
Trevor:
I have done some research and found more info... I am working on a quick solution
Trevor:
Apparently there is a "bundle bit" that can be toggled for a folder to make it a package. If this bundle bit is missing, the package shows as a folder instead of a folder
Trevor:
Mozy apparently has the same issue as iDrive for the Quicken data file when recovered
Trevor:
by toggling the bundle bit for the folder, it becomes a package (with Mozy's recovered file/package)
Trevor:
I am currently testing to see if this works for the file recovered from iDrive
Trevor:
i need 2 more minutes... almost there
Technical Support:
Ok Trevor. We thank you for the information. I will forward this to our development team for further analysis.
Trevor:
unfortunately, when toggling the iDrive recovered file/folder bundle bit, the contents are so corrupted that the file is unreadable by Quicken.
Trevor:
Will I hear back from iDrive regarding this issue?
Technical Support:
Yes Trevor. We will get back to you via email (rovertpressman@gmail.com).
Technical Support:
Is there anything else with IDrive I may assist you at the moment?
Trevor:
aliases have become corrupt, and more files become corrupt within the package...
Trevor:
I cannot see how iDrive can be considered compatible. Of all things for it to fail on, personal financial data is one of the worst!
Trevor:
You should test this on the OS X iphoto photo library as well - it is a package and is more than likely corrupt and unrecoverable when backed up with iDrive.
Trevor:
I have to switch back to Mozy now. Hope to see this major bug fixed in a future release.
Technical Support:
Trevor, we will analyze this further and determine the cause to fix it. We will get back to you with an update on this at the earliest.
Trevor:
thanks
Technical Support:
You are welcome Trevor.
Please login or create a new MacUpdate Member account to use this feature
Watch Lists are available to MacUpdate Desktop Members Upgrade Now
Download and auto-install
using MacUpdate Desktop. Save
time moving folders and cleaning-up.
IDriveforMac is a user-friendly, secure and reliable application that performs automated online backup of your files and folders.
The application safeguards your critical data in case of a system crash. The graphical interface is coupled with powerful scheduling and logging features.
Incremental backups - only modified portions of files are backed up, thereby conserving bandwidth
Data compression during transmission that lead to quick backups
Enhanced security with 128-bit SSL encryption on data transfers
Network or Mapped Drive backup support
Automatic backup of critical data including the Desktop, Downloads, Documents, Music, Movies and Pictures folders
Locate files and folders backed up to your account and restore the same to your Mac desktop
Snapshots allow you to retain changed data history over a period of time
Provision to regulate the Internet bandwidth usage with the Bandwidth Throttle feature more
Provision to perform interactive backups/restores or schedule backups for a future date and time
'Automatic Power off' option after a scheduled backup - the machine shuts down automatically once data is backed up
+25
+3
x86tech reviewed on 04 Nov 2011
+153
Virgeist reviewed on 31 Oct 2011
Overall it seems like a very decent app, though I would like to be sure I can trust the developer before sending them my most sensitive data.
+52
IDrive Basic (the free option) now provides 5GB of storage space.
Pricing plans for the various "Pro" versions are here:
https://www.idrive.com/pricing.htm
+27
Personally, I wouldn't trust my valuable or sensitive data to some storage facility in God-knows-where.
But, to each his/her own.
-4
+33
+1
+1
+4
+940
There's a lot of value in off-site backups. And as others have said, there's multiple ways to encrypt your data before you send it anywhere
+9
If you are mistrusting of the provider and think they can / will read your stuff, then encrypt the data before you copy it there. MacFuse is your friend here.
Some handy instructions (hopefully the links are OK):
http://www.hutsby.net/2011/06/howto-using-encfs-with-dropbox-on-osx.html
http://www.hutsby.net/2011/05/getting-started-with-truecrypt-and-osx.html
+4
+13
kaz219 reviewed on 21 Jun 2009
Another problem in my opinion is the memory usage. Right now, with *no* backup going on, it uses 150MB RAM ("real memory" column in activity monitor) which is quite a lot for a background daemon...
Otherwise it's ok, and still a better (or "less worse") interface than the one from Mozy (where you can't even get rid of the menu bar item - mine is already cluttered, I really don't need another item there.).
+73
1. Could you please post revision notes? There's been two in about a week.
2. Sparkle updating would be very nice.
Thank you!
+3
+242
Dana Sutton reviewed on 15 Apr 2009
Also, anybody with a fairly large body of data that needs to be backed up should be aware that the initial upload is going to take a long time (mine took over five days). If you aren't very cool about using the bandwidth throttle you're internet performance is going to take a massive hit.
+1
"The available daily Snapshots have been set to 10 (This may change without notice). The additional storage requirements for Snapshots have no impact on your account quota usage."
Once 150GB is filled, you can simply add an additional account and control from the same software. Honestly, I don't see the issue with providing 300Gb for double the cost, but, they don't seem to offer that right now and simply allow you to buy as many accounts with 150GB as you want....
+2
+73
I (and many other people) want simple, automatic mirroring of folders. This can't be that hard.
+5
+28
SFurst reviewed on 22 Mar 2009
Unfortunately, the Mac client serious lags behind the Windows client. As pointed out by numerous reviewers, there is no data encryption available for Mac, leaving your files unencrypted on the servers. While the web site claims versioning, this is only available for Windows; a poor substitute "Snapshots" is available for Mac, which makes you go through the last ten backups searching for a previous version. In my experience, Snapshots were unreliable as well as tedious (think Time Machine, only very limited). If I want a previous version of a file, I want to see what versions are available, not have to dig.
Unlike SpiderOak and JungleDisk, the same storage cannot be shared between a Mac and a PC client. A web interface is available.
Support from the developer is responsive but unhelpful. "Encryption is being consider in the future and we will notify our customers when it is available".
I suspect this is quite a nice program on the PC, but it has a long way to go for us Mac users.
iDrive is incompatible with OS X package files as well as legacy Mac OS files that contain resource forks.
A common file that you would want to backup: QUICKEN DATA
After recovering your Quicken Mac 2007 data file, you will quickly realize that the package file has become a folder and the contents of the package file (now a folder) are all corrupt and unrecoverable!
Mozy, as slow and unreliable as it is, at least doesn't corrupt the contents of the package file - but it does change the package file into a folder. You have to use a utility like FileMatey (Google it) it convert the recovered folder back into a package, and then it works. With iDrive, this is NOT the case.
I don't want to SPAM too much in this comment, but I want to post my iDrive tech support transcript to show that they confirm the issue, so here it is (sorry it's long):
Chat Transcript
Visitor: Trevor
Operator: Technical Support
Company: dx_tests
Started: 15 Jul 2010 11:13:45
Finished: 15 Jul 2010 11:57:26
Trevor:
I'm attempting to recover a backed up Quicken file for Mac and it appears that iDrive has corrupted all of my backed up Quicken files...
Call accepted by operator Technical Support. Currently in room: Technical Support.
Technical Support:
Hello Trevor, you are chatting with Karthik.
Technical Support:
How are you today?
Trevor:
ok
Trevor:
are you familiar with Mac OS X files?
Trevor:
specifically a Mac OS X package file?
Technical Support:
Yes. Let me see what I can do Trevor.
Could you please let me know if you are receiving any errors?
Trevor:
no errors. The file/package is being backed up by iDrive on an automated schedule. When I recover the file/package, it is recovered as a FOLDER instead of a package file and the contents are corrupt. The backup is useless... your FAQ states that customers should ZIP the pagage files before backup - this defeats the automated purpose of iDrive
Trevor:
Any way I can get the package file restored?
Technical Support:
Trevor, let me check this issue from our end and will let you know what could be done.
Technical Support:
Please give me few minutes.
Trevor:
here is a link to your FAQ - http://www.idrive.com/online-backup-mac-faq.htm#12sub
Technical Support:
Trevor, could you please let me know if this package file in your account is being displayed as a folder or not?
Trevor:
its being displayed as a folder in iDrive.
Trevor:
and it is also a folder when recovered from iDrive back to my Mac
Trevor:
it is a package file originally on the Mac
Trevor:
I'm reading the FAQ - it states that iDrive doesn't backup files with resource forks and it also states that it may fail with package files...
Trevor:
Bottom line, iDrive is NOT compatible with Mac OS X. You should not be selling it to Mac users because you are giving them a false sense of security.
Technical Support:
Trevor, IDrive for Mac application is compatible with Mac OS X. We have tested this and there are many customers using without issues.
Currently, could you please send us the log files from the application? Use the Send Error Report feature. You can find the Send Error Report feature when you right click on the IDrive Tray Icon and then click Send Error Report. Alternatively, you can find it under the Help menu, after you login into IDrive application.
Trevor:
there are no error reports. I don't feel that you are completely understanding what I am talking about.
Trevor:
the customers that are using it are unaware that they have been mislead. they are "using it without issues" because they don't know that they are losing data
Trevor:
where do you want me to send the error report?
Trevor:
what is the trouble ticket number?
Technical Support:
Trevor, the error report is a consolidated log that lets us know if there are any issues with the functionality of the application. This helps us in determining the issue effectively.
Trevor, ignore the ticket# field for now. Fill in your details and submit.
Technical Support:
Trevor, we have not had any such reports. We have many customers who are backing up packages without issues. They are able to restore them as well. In this case we need to analyze what could have happened.
Trevor:
report sent successfully
Technical Support:
Ok. Let me check. Please give me 2 minutes.
Trevor:
how can you say this when it is listed in your FAQ?
Trevor:
you're lying to me!?
Trevor:
The IDrive for Mac application has not backed up some files inside the bundle / file package. Why?
This could be because the files are Mac OS X files or hidden or the file names contain special characters. We recommend that you compress (zip) the entire bundle / file package and try backup.
Trevor:
Does IDrive for Mac backup files that contain extended attribute i.e. resource fork data?
No. IDrive for Mac does not backup files that contain extended attributes i.e. resource fork data.
Trevor:
these two FAQ items make iDrive incompatible with Mac OS X.
Technical Support:
Trevor, could you please let us know the name of this package file?
Trevor:
Main Accounts
Trevor:
located in users/trevor/documents/quicken data/main accounts
Trevor:
main accounts is the package file
Trevor:
FYI the files inside of the package file are also being corrupted - most likely because they contain resource fork information.
Technical Support:
Trevor, we need to consult our development team on this. We will get back to you via email with an update at the earliest.
Trevor:
I have done some research and found more info... I am working on a quick solution
Trevor:
Apparently there is a "bundle bit" that can be toggled for a folder to make it a package. If this bundle bit is missing, the package shows as a folder instead of a folder
Trevor:
Mozy apparently has the same issue as iDrive for the Quicken data file when recovered
Trevor:
by toggling the bundle bit for the folder, it becomes a package (with Mozy's recovered file/package)
Trevor:
I am currently testing to see if this works for the file recovered from iDrive
Trevor:
i need 2 more minutes... almost there
Technical Support:
Ok Trevor. We thank you for the information. I will forward this to our development team for further analysis.
Trevor:
unfortunately, when toggling the iDrive recovered file/folder bundle bit, the contents are so corrupted that the file is unreadable by Quicken.
Trevor:
Will I hear back from iDrive regarding this issue?
Technical Support:
Yes Trevor. We will get back to you via email (rovertpressman@gmail.com).
Technical Support:
Is there anything else with IDrive I may assist you at the moment?
Trevor:
aliases have become corrupt, and more files become corrupt within the package...
Trevor:
I cannot see how iDrive can be considered compatible. Of all things for it to fail on, personal financial data is one of the worst!
Trevor:
You should test this on the OS X iphoto photo library as well - it is a package and is more than likely corrupt and unrecoverable when backed up with iDrive.
Trevor:
I have to switch back to Mozy now. Hope to see this major bug fixed in a future release.
Technical Support:
Trevor, we will analyze this further and determine the cause to fix it. We will get back to you with an update on this at the earliest.
Trevor:
thanks
Technical Support:
You are welcome Trevor.
+3
x86tech rated on 04 Nov 2011