About the moveItemsBetweenReplicaVaults Property
When content replication is configured, the replication process from the master site to the remote sites is performed in several steps.
Before objects are delivered to the remote sites, the following two queries take place:
• Windchill determines which objects must be moved between replica vaults. Moving objects between replica vaults occurs when:
◦ The corresponding WTObject has been moved from one domain to another.
◦ The life cycle state of the object has changed.
◦ The replication rules have been modified.
• Windchill determines which objects must be replicated from the master site to the remote sites. Only objects that have been replicated are moved. Objects that were created with the preference set to replica are not moved unless they also exist on the master site.
The first query can be very time consuming. You can use the wt.fv.master.moveItemsBetweenReplicaVaults property to disable the first query. If the wt.fv.master.moveItemsBetweenReplicaVaults property is set to true, objects can be copied between vaults on the same remote site. If the target vault is on the same site as the upload vault, the content file is duplicated in the cache vault and not removed unless you reset replication or reset undelivered replication items through the Vault Configuration window. Set this property to false to improve site performance.
|
|
PTC recommends one vault per remote site for content replication, and two vaults per remote site for upload caches. Only one vault is actively used at any point in time.
|
