It was announced many months ago. Do you have any estimate of when it will be ready for prime time? I am very interested in the versioning provision. I use ACDU.
It has taken us longer than we thought to get backup out, but it is still coming. We will be sure to announce it the second it is ready for prime time.
This feature would further the case for odrive in a business environment. I’ll use our setup as an example. We have multiple users all with at least one workstation and a laptop or three. A number of our shared folders have a designated owner; other users can read or sometimes add files but only the owner or admins can delete. Other folders only have delete access by an admin user. The master copy for these folders typically is on one of our servers, while the user-specific ones have the master on a workstation.
For many of the folders we restrict delete access (change sometimes as well, although we can always roll back using cloud versioning) to a specific user and computer. In other words, if my laptop drive becomes corrupt or I wipe a folder by mistake after working too late one night, I don’t want the cloud sync propagate the deletions onward. Admins can delete from anywhere, but these credentials aren’t used for normal logins.
We had this setup with Box for Biz. Pricing became crazy, so we migrated to AWS. Mimicking the Box permissions is a major PITA. If odrive provided a means of handling these cases independently of the storage back end, we’d be ecstatic. Of course synchronizing would have to work reliably as well.
It’s been another month since this thread’s last update. Any news on when odrive’s Backup capability will be available?
As we were going through backup, our new iteration of encryption, and sync enhancements, we realized that we needed to restructure some underlying core components of the engine. This restructuring will allow us to deliver these features optimally and ensure that we can rapidly develop future enhancements and features.
We are still in the process of working through these core components, which is why features like backup, new encryption, and others are still pending. We apologize for the delay, but we want to make sure we deliver quality to our users.
I don’t have any dates to give, but I can tell you that these things are high priority for us and the team is cranking away.
Is the backup feature going to allow incremental backups?
Backup will be incremental, by nature. It will detect changes occurring locally and only push those changed files up. If the file has been updated (instead of being a brand new file) it will be created as a version.
Will the engine support backup of external drives that aren’t always plugged in? This would make odrive invaluable to us!
Yes. odrive will be able to deal with the drive “disappearing” and “reappearing” at a later time.
Great feedback on 10/10/2016, Tony. Thank you. Any updates? If it’s another thread or announcements (hint, hint) then just point us in the right direction.
Is a “work around” to backup while waiting till the update comes to use the “Sync to odrive”? E.g., I use OneDrive and Google Drive for my personal and work files, respectively, and Amazon Drive for backup:
- If I stored OneDrive and Google Drive in separate folders (i.e., not odrive) on my computers
- Use “Sync to odrive” to tie those separate folders to odrive
- Set Sync settings read “store nothing”
- Set Unsync (?) settings remove files immediately so I don’t duplicate space
- Also set “Sync to odrive” to tie those separate folders to my backup on Amazon
Then I suppose I’d have a second copy, but not a backup, since odrive would delete files from the backup. I might be able to get around this by setting Delete to never, but that’d suck for sorting out which files to delete vs. keep/undo since odrive doesn’t show which cloud the deleted files belong to (nor should it).
Anyway…just contemplating “out loud.” I think I’d rather wait for the backup capability of odrive. That’s what we’re paying for, anyway, right?
Your thinking is correct. Sync can be considered a form of backup. There are plusses and minuses to using full, bi-directional sync to “backup” your data. Since we don’t have traditional backup available, there are users that use “sync to odrive” for their own backup use case.
Sync is a much heavier process than traditional backup, so when you apply sync to more massive data repositories, like multi-terabyte external drives, or NAS, it can make odrive work really hard to continually ensure that both sides are always consistent. This can create some CPU heat, large memory footprints, and excessive network calls. Sync also needs to be much more aggressive than traditional backup, since a key component of a good sync engine is speed of reflection on both sides. In a traditional backup use case much of this sync work is wasted, because the user is never going to change anything on the remote side and local changes do not need to be reflected as quickly as possible.
Sync will sync any remote deletes to local, which is usually not something you would normally want in a traditional backup scenario. Additionally, sync has the potential to also push local deletes to the remote, which is also not something you generally want for a traditional backup. We do have the odrive trash as a safeguard against unwanted local->remote deletes, but, as you noted above, if would be a pain to have those pending deletes hanging around in the odrive trash, forevermore.
In my case, I use “sync to odrive” on the important folders on my local systems that are heavily used, as a “working backup”. Folders like: Documents, Desktop, Downloads, Pictures, Music, and Videos. The names may very slightly between OSs, but I have these default OS folders all mapped to corresponding locations in Amazon Drive.
Generally speaking, most of the files I work with on a day-to-day basis are in these locations. Mapping things in this way allows me to sync changes and additions, without me having to change any default behavior. It creates a cloud-merged view of these folders across all of my systems. Everything I touch, on any system, is automatically backed-up to the remote storage and then synced down to my other systems as placeholders or locally cached files, depending on the location and use case.
Since many applications like to default to these locations, it gives me the advantages of cloud storage and multi-system mirroring without having to configure these applications to use non-default paths. With this type of setup I also have the flexibility to move any placeholders to any other locations that are mapped. So I can move a placeholder from my Downloads folder to my Documents folder or to my Desktop. This move is reflected in the cloud and across all of my devices.
Long story short (too late), odrive is not the same as “traditional backup” and may not be the right solution for you in cases where you are working with multi-terabyte data sets, are not interested in any two-way reflection, or want to remove all possibility of deletes. For use cases that fall outside of that, the default odrive folder or “sync to odrive” folders can be very useful features and ones that I have found to be fundamentally transformative in my own use of the my local systems, and cloud.
More information on “sync to odrive”: https://docs.odrive.com/docs/manage-sync#section-sync-external-folders
Just wanted to check in if you have any news about the backup functionality, any release date in sight?
Or are there significant problems that it will take (a lot) longer? If so, I will re-asses my backup situation (I have no cloud backup running at the moment, after prematurely ending my crashplan membership in exchange for odrive backup).
Hopefully in time for Christmas
It is still being worked on. It probably won’t be available before Christmas, but are hoping to be able to release something within the next 8 weeks.
6 weeks further down the line. Apologies for stressing this issue, it just feels uncomfortable not having a backup running.
Any end in sight, or could we expect it later this year?
Bump. Any news? It’s way after Christmas now
Hi there I am very happy with this tool. I want to advise all that I have tryed the BACKUP function.
IT WORKS !!! The Command should be passed like so :
python “$HOME/.odrive-agent/bin/odrive.py” backup “temp/” “/OneDrive For Business/”
The explaination is : “temp” should be your local folder to save and
"/OneDrive For Business/" the Absolute Path for the Remote Folder on
your One Drive For Business Storage. So if you have Dropbox change it
To make it scriptable you can fix the Tony’s one :
agentmount="$HOME/odrive-agent-mount/OneDrive For Business/“
echo “CHECKING odrive mount point …”; sleep 2;
[[ $(python “$HOME/.odrive-agent/bin/odrive.py” status | grep “Mounts:
1”) ]]; then echo “MOUNT FOLDER CORRECTLY MOUNTED”; else echo “Please
Mount odrive Folder … Aborting Script”; exit 1; fi
cp -R “$sourcedir” “$targetdir”;
echo “STARTING THE BACKUP …”
python “$HOME/.odrive-agent/bin/odrive.py” backup “temp/” “/OneDrive For Business/”
Any news on the release date?
Thanks for sharing.
The backup feature you see in the CLI a very, early-stage preview of backup. It kind of snuck into the CLI way back when we first released the odrive Agent. We didn’t remove it because there isn’t really any chance of “misusing” it and the fact that it is in the CLI lends itself to only being seen/used by more advanced users. Backup is a much simpler data flow, compared to sync, since all of the data flows in a single direction and there are no deletes/moves/etc, so you can’t really get into trouble using it.
I do want to stress that it should be viewed as a “beta”, at best.
We are still working on it as part of the next major version of odrive. I know it is frustrating that it isn’t out yet. We have ended up doing a lot of work on the internals of the sync engine which will allow us to build and refine much quicker than we were able to before.
Unfortunately this type of work is time consuming, but its an investment in the future.
are we talking about days or month?