Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
provider-synchronization [2023_06_22 05:41] – external edit 127.0.0.1 | provider-synchronization [2024_04_22 21:30] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
# Provider Sync and Cloud Refresh | # Provider Sync and Cloud Refresh | ||
- | **Last updated | + | **Last updated |
- | The Enterprise File Fabric | + | Access Anywhere |
- | Applications may update/ | + | Applications may update/ |
See also: [[real-time-cloud-refresh|]]. | See also: [[real-time-cloud-refresh|]]. | ||
Line 21: | Line 21: | ||
* **Deep Cloud Refresh** can be selected when browsing via the web will also re-sync sub-folders. This operation runs as a background task. | * **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, | * **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. | + | * **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. This setting applies only to folders that are open in the File Manager. |
- | More information on Cloud Refresh, Deep Cloud Refresh and Real-time refresh can be found [[cloudappliance: | + | More information on Cloud Refresh, Deep Cloud Refresh and Real-time refresh can be found [[server: |
. | . | ||
### Scheduled | ### Scheduled | ||
- | * **Periodically** – To update the metadata for an entire account (provider), a “Provider Re-sync” or " | + | * **Periodically** – To update the metadata for an entire account (provider), a “Provider Re-sync” or " |
### On Provider Event | ### 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. | + | 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/folder | ||
+ | * copy file/folder | ||
+ | * rename file/folder | ||
+ | * delete file/folder | ||
+ | * cloud refresh | ||
+ | * deep cloud refresh | ||
===== Improving Synchronization Speed ===== | ===== Improving Synchronization Speed ===== | ||
- | When the Enterprise File Fabric | + | When Access Anywhere |
- | Out of the box, the File Fabric's synchronization process will be confined to a single system process. The performance speed of the initial synchronization process is configurable which will help you reduce the time it takes for initial synchronization. | + | Out of the box, Access Anywhere's synchronization process will be confined to a single system process. The performance speed of the initial synchronization process is configurable which will help you reduce the time it takes for initial synchronization. |
To change the number of threads to be used for initial sync and re-syncs as ApplAdmin change this value under "Site Functionality": | To change the number of threads to be used for initial sync and re-syncs as ApplAdmin change this value under "Site Functionality": |