Please note that we don't actually offer a bespoke profile/schema design service, but I'll offer some advice for this exception.
You can try creating an Intelligent Synchronization profile, but note that Sync is strictly a two-way comparison process (A-to-B, B-to-A) and we typically do not recommend users to sync to multiple devices as unwanted overwrites/deletes on files could easily occur if a strict running order sequence is not met.
It is possible to set up a few profiles to multi-sync them across several devices. However, there are several important details/drawbacks to take note of when making a schema of multi-way sync profiles.
The process will require at least the following steps to ensure complete file synchronization.
1. Home PC <sync> Ext Drv
2. Office <sync> Ext Drv
3. Home PC <sync> Ext Drv
Step 3 is required for changes in Step 2 to be synced back to A.
IMPORTANT NOTE - Please ensure that you are running this design order as per the listed sequence so that data changes in all locations are properly synced. Don't run these profiles concurrently or all at once. Don't skip any steps.
It is important to note that no two (or more) users/PCs can work on the same local file/s at the same time in-between such a schema sync. This would introduce multiple versions of the file (containing different sets of data) to be present on different machines. When the sync process triggers, it will cause the eventual overwrite of one over the other (whichever file with the older Last Modified time stamp will be replaced by the newer, thereby changes in the older file is never replicated and lost forever).
During the schema run/multi-run period, do not let any user or process make any file changes/deletion within these devices or collisions will likely occur.
Do note that if any other process(es) upload any files to this 'group', they would not have the meta-data we use and rely on so they might be processed in unexpected ways.
You can try creating an Intelligent Synchronization profile, but note that Sync is strictly a two-way comparison process (A-to-B, B-to-A) and we typically do not recommend users to sync to multiple devices as unwanted overwrites/deletes on files could easily occur if a strict running order sequence is not met.
It is possible to set up a few profiles to multi-sync them across several devices. However, there are several important details/drawbacks to take note of when making a schema of multi-way sync profiles.
The process will require at least the following steps to ensure complete file synchronization.
1. Home PC <sync> Ext Drv
2. Office <sync> Ext Drv
3. Home PC <sync> Ext Drv
Step 3 is required for changes in Step 2 to be synced back to A.
IMPORTANT NOTE - Please ensure that you are running this design order as per the listed sequence so that data changes in all locations are properly synced. Don't run these profiles concurrently or all at once. Don't skip any steps.
It is important to note that no two (or more) users/PCs can work on the same local file/s at the same time in-between such a schema sync. This would introduce multiple versions of the file (containing different sets of data) to be present on different machines. When the sync process triggers, it will cause the eventual overwrite of one over the other (whichever file with the older Last Modified time stamp will be replaced by the newer, thereby changes in the older file is never replicated and lost forever).
During the schema run/multi-run period, do not let any user or process make any file changes/deletion within these devices or collisions will likely occur.
Do note that if any other process(es) upload any files to this 'group', they would not have the meta-data we use and rely on so they might be processed in unexpected ways.
Statistics: Posted by Conrad Chung — Sun Dec 23, 2018 4:02 pm