Have the capability to STOP the replication (synchronization) between files servers and the master with only ONE Master Vault and with option "forceContentToVault" to "true".
| Symptômes | Even if you set properties "wt.fv.master.adhocCaching.flag" to "false" and "wt.fv.predictiveReplicationEnabled" to "0", there is always a synchronization appear every 3 hours which copy all new files from the Files Servers to the Master server. |
|---|---|
| Étapes à reproduire : | We can imagine to have new property to stop synchronization. A future setting could be: set « forceContentToVault » to avoid managing rules, set « wt.fv.useFvFileThreshold » and « wt.fv.fvFileThreshold » to avoid managing folders, set user preference vaulting to manage where files must be send between « master » and « Files Servers ». By default it is the "master. set « wt.fv.master.adhocCaching.flag » to "0" to avoid adhoc replication, create a new prop like « wt.fv.master.synchroDisabled » to "true" to stop synchronize every 3 hours set « wt.fv.predictiveReplicationEnabled » to "false" to disable predictiveReplication. Consequence: We know taht we have to manage backup properly between master and files servers because files are NOT on the Master site. |
This new feature can simplify the capability to avoid synchronization between Files servers and Master. This feature is need for example for security reason. If you work across country and it is mandatory that parts created in a specific country MUST stay in this country. No replication to the Master site. Behind that there is a governemnt law to control that. I know it is possible for the moment by using several Masters vaults but it is complex to manage and you lost the capability to use the "forceContentToVault". unbelievable, we can't imagine that!