Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
provider-synchronization [2019_05_30 15:40] – dan | provider-synchronization [2024_04_22 21:30] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | # Provider |
- | When the Enterprise File Fabric initially connects | + | **Last updated Oct. 11, 2023** |
+ | |||
+ | Access Anywhere indexes storage providers | ||
+ | |||
+ | Applications may update/ | ||
+ | |||
+ | See also: [[real-time-cloud-refresh|]]. | ||
+ | |||
+ | ## Synchronization Options | ||
+ | |||
+ | There are a number of ways that the metadata can be updated, on demand, scheduled and on provider change. | ||
+ | |||
+ | ### On Demand | ||
+ | |||
+ | There are several options for initiating | ||
+ | |||
+ | * **Provider | ||
+ | * **Cloud Refresh** can be selected when browsing via the web, mobile or desktop apps. This user driven action will re-sync | ||
+ | * **Deep Cloud Refresh** can be selected when browsing via the web will also re-sync sub-folders. This operation runs as a background task. | ||
+ | * **Real-time refresh** can be enabled on the provider which updates | ||
+ | * **Folders auto-refresh** is a provider setting similar to a real-time refresh but the folder refresh is started asynchronously. Results will be available when the user returns to the folder. | ||
+ | |||
+ | More information on Cloud Refresh, Deep Cloud Refresh and Real-time refresh can be found [[server: | ||
+ | . | ||
+ | ### Scheduled | ||
+ | |||
+ | * **Periodically** – To update | ||
+ | |||
+ | ### On Provider Event | ||
+ | |||
+ | Many providers are able to create events on object or file creation or deletion. These can be sent and processed by Access Anywhere. This is the approach [[jibe|Jibe]] uses. | ||
+ | |||
+ | |||
+ | ===== Blocked Operations ===== | ||
+ | The following operations are prevented when a provider is being sync'd (initial sync or re-sync): | ||
+ | * move file/ | ||
+ | * copy file/ | ||
+ | * rename file/ | ||
+ | * delete file/ | ||
+ | * cloud refresh | ||
+ | * deep cloud refresh | ||
===== Improving Synchronization Speed ===== | ===== Improving Synchronization Speed ===== | ||
- | Out of the box, the File Fabric's synchronization process will be confined to a single system process. | + | When Access Anywhere initially connects to your storage platform, it performs a full provider synchronization. In this process, Access Anywhere builds a metadata model for your storage platform, recording information such as the files and folders that are there. At this stage, Access Anywhere does not download or read any of the files, instead, it simply records the metatdata of the files. |
+ | |||
+ | Out of the box, Access Anywhere's synchronization process will be confined to a single system process. | ||
- | To set the number of threads to be used for tis initial | + | To change |
- | < | + | * Maximum count of parallel Cloud Sync tasks |
- | var $initialsyncthreads = 2; | + | |
- | </ | + | |
The number set here will control the number of concurrent processes permitted to run for a single synchronization task running on your appliance. | The number set here will control the number of concurrent processes permitted to run for a single synchronization task running on your appliance. | ||
You should take care when choosing an appropriate value, as high values could cause performance impacts to the overall platform. | You should take care when choosing an appropriate value, as high values could cause performance impacts to the overall platform. |