Once a batch of data has synced, you can unsync those files and load in the next ones. The gigabytes of data that you may have strewn about on different computers, external hard drives, NAS, and flash drives can all be stored in the cloud using odrive.
You can now collapse structures that you want to archive away, or keep from your current focus.
It also reduces your data sprawl, allowing you, and odrive, to work in a more focused and efficient manner. It signals the end of the project and frees up the space for the next one.
The need for unsync can be as simple as wanting to free up some extra space for that new game, application, or movie, but there are more advanced use cases for unsync that can help you enhance your workflow or allow you to truly “live in the cloud”. The result would be a single “My Photos.cloudfx” placeholder file in its place and an additional 100GB of available space on your local disk! All of the content in “My Photos” is now safely tucked away in the cloud for later access. A simple right-click->unsync action on “My Photos” would go through all files within that folder structure, check to make sure each one was successfully synced to Amazon Cloud Drive, and, once verified, would unsync the entire “My Photos” folder. Now you want to free up that space locally. For example: Let’s say you copied in 100GB of photos into a directory inside your linked Amazon Cloud Drive account (My Photos) and, after a time, it all synced up to the cloud.
odrive collapses everything in that folder down to a single placeholder file, freeing up all of the space that was previously occupied by the entire structure. Unsyncing folders works in much the same way, except that it applies file unsync to all of the files below the specified folder structure, no matter how deep it goes.