ICLOUD SYNC FOLDER DOWNLOAD

ICLOUD SYNC FOLDER DOWNLOAD

“Evict downloaded files” will evict any file that ChronoSync must download to complete a sync, after it has determined it is finished using it. The following sections provide common examples of these two scenarios in which you would use ChronoSync with iCloud. In this case you simply want to keep your backups stored in iCloud, to be retrieved only if you need to restore lost or corrupted data. This would typically be done when you are NOT storing files in application-specific containers and/or you are NOT synchronizing your Desktop and Documents folder with iCloud (or you don’t store your working data beneath Desktop and Documents). The second scenario where ChronoSync can effectively be used with iCloud is to use iCloud to store backups of your data. In such cases, it is important to have backups of your iCloud-stored files in case they get accidentally deleted or corrupted, either through user error or a problem with the iCloud service. This is useful when you are actively working with documents stored on iCloud, either through the specific application’s own container or when you are synchronizing your Documents and Desktop folder with iCloud. This typically involves taking files stored in iCloud and copying them to an external drive connected to your Mac, or maybe even another cloud service. The first is to backup the files you already have stored in iCloud. There are two main scenarios where ChronoSync can effectively be used with iCloud. All this support gives ChronoSync the unique capability to backup/sync to/from iCloud containers without filling up local storage. Lastly, ChronoSync can detect when a file is being uploaded to iCloud and can wait for such uploads to complete before moving on. It can also automatically evict files copied to iCloud storage and/or evict any file that needed to be downloaded in order to perform a backup/sync operation. The iCloud-specific enhancements to ChronoSync allow it to identify placeholder files and trigger downloads when necessary. They must also be able to identify when such downloads are complete before they attempt to read their data. If an application wants to read the contents of such files (perhaps to copy them), they need to take explicit actions in coordination with the OS to trigger their download from iCloud. Applications thus need special logic to identify these placeholders as such and to determine what file they are supposed to represent. The problem with this scheme, from an application perspective, is that the placeholder files are invisible files and are not named the same as the file they represent.

More likely, the application will not do anything with the file and just let the OS determine when a file needs to be evicted to reclaim local storage space. That’s because at this point, it IS stored locally! Once an app has finished using a file, it can be evicted to conserve space until it is needed again.

Once complete, the downloaded version replaces the placeholder, and the file can be opened as if it were stored locally. If a user or app tries to open an evicted file, it is automatically downloaded from iCloud. The process of removing a local copy of a file and creating a placeholder for it is known as eviction. This removes the local copy of the file but leaves a small placeholder on the local device so that it appears as if the file is still stored there. In order to conserve local storage space, files stored in an iCloud container can be evicted.

Icloud sync folder