Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
provider-synchronization [2019_05_28 12:43] – smeadmin | provider-synchronization [2023_10_11 06:21] – dan | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | # Provider |
- | When the Enterprise File Fabric initially connects to your storage platform, it performs a Provider Synchronization. In this process, the File Fabric builds a metadata model for your storage platform, recording information such as the files and folders that are there. At this stage, the File Fabric does not download or read any of the files, instead, it simply records the metatdata of the files. | + | **Last updated Oct. 11, 2023** |
- | ===== Improving Syncronization Speed ===== | + | The Enterprise File Fabric indexes storage providers to provide a number of enhanced file services including fast browsing and search. The File Fabric has its own indexing engine to provide these services. |
- | Out of the box, the File Fabric's syncronization process will be confined to a single system process. As of File Fabric | + | Applications may update/ |
- | To set the number of set / replace | + | See also: [[real-time-cloud-refresh|]]. |
- | < | + | |
- | var $initialsyncthreads | + | ## Synchronization Options |
- | </code> | + | |
+ | 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 a refresh both user-initiated and automatic: | ||
+ | |||
+ | * **Provider Resync** can be initiated from the Dashboard | ||
+ | * **Cloud Refresh** can be selected when browsing via the web, mobile or desktop apps. This user driven action will re-sync the folder as needed. | ||
+ | * **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 metadata automatically, | ||
+ | * **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 [[cloudappliance: | ||
+ | . | ||
+ | ### Scheduled | ||
+ | |||
+ | * **Periodically** – To update the metadata for an entire account (provider), a “Provider Re-sync” or " | ||
+ | |||
+ | ### On Provider Event | ||
+ | |||
+ | Many providers are able to create events on object or file creation or deletion. These can be sent and processed by the File Fabric. 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/folder | ||
+ | * copy file/ | ||
+ | * rename file/ | ||
+ | * delete file/ | ||
+ | * cloud refresh | ||
+ | * deep cloud refresh | ||
+ | |||
+ | ===== Improving Synchronization Speed ===== | ||
+ | |||
+ | When the Enterprise File Fabric initially connects to your storage platform, it performs a full provider synchronization. In this process, the File Fabric builds a metadata model for your storage platform, recording information such as the files and folders that are there. At this stage, the File Fabric does not download or read any of the files, instead, it simply records the metatdata of the files. | ||
+ | |||
+ | Out of the box, the File Fabric' | ||
+ | |||
+ | To change the number of threads to be used for initial sync and re-syncs as ApplAdmin change this value under "Site Functionality": | ||
+ | |||
+ | * Maximum count of parallel Cloud Sync tasks | ||
+ | |||
+ | 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. |