I would appreciate knowing 1: whether this feature has already been requested (or at least if this issue has been reported before), 2: a rough time-to-implement this feature. Last but not least: when you respond to this, please do not give a generic "your feedback is valuable and we have sent it to our development team". Then I can have CDP enabled and *still* have daily backups, because they won't take forever! Please look into how to integrate the CDP tech into your full backup so that large data sets like mine do not take many, many hours to backup. However it is going to miss my Lightroom catalog, which is a problem. My last backup looked at all 1.3 million files, but *only 47 of them had changed*! With the change I am suggesting, the backup process would have probably taken only 5-10 minutes as only 1 of those 47 files was larger than 500MB.įor now I will enable CDP and set my backups to weekly. ![]() This will almost certainly happen very quickly by comparison. All you need to do to make the backup faster is use the CDP method, and then when the full backup happens, *just* look at files >500MB. I would suggest taking the change detection technology of CDP and using it to *inform the complete backup process*. But I do have a couple of files (my Lightroom catalog, in particular) that are larger than 500MB and need regular backup, so CDP is not a total solution for me. That's fine, it makes sense not to try to backup 500MB or larger files on that frequent of a schedule. That's a great feature, but of course it doesn't deal with files greater than 500MB. In fact iDrive does already have a feature - Continuous Data Protection - which apparently *can* detect what has changed, in realtime. That is not a very good way to handle change detection, and any good backup program has already implemented a smarter way to deal with it. ![]() Only a small percentage of these files change between each daily backup, yet the backup process takes about *14 hours* every single time! Why? It seems to be because iDrive has no way to actively detect what files have changed or been added, and so it spends those 14 hours to scan every single file to see if it has been updated. I have a 3TB backup set and about 1.3 million files.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |