Enterprise Administration > File Vaulting and Replication > Replication > Understanding Replication > Editing Replication Properties > Master and Remote Site Properties
  
Master and Remote Site Properties
The following table shows the properties that you can set on master sites, remote sites, or both.
Property
Master Site
Remote Site
Description
wt.fv.master.verboseProperties
X
Prints master service properties when the method server starts.
wt.fv.master.verbose
X
Verbose setting for master service. Prints to the method server log file.
wt.fv.purgeNotReplicatedItemOlderThan
X
Specifies the time period for which files that did not replicate properly become unreferenced. The default value is 2 days. Values less than 2 days will be ignored.
wt.fv.master.replicatePrevCleanedObjects
X
If set to false, prevents files that were cleaned up by using the automated cleanup options from being replicated. The default setting is true.
wt.fv.revaultQuerySize
X
Specifies the maximum number of objects to be replicated and retrieved in one query to the database.
wt.fv.replica.verbose
X
Prints replica service properties when the method server starts.
wt.fv.replicationFileSizeThreshold
X
Specifies the minimum file size to be eligible for replication.
wt.fv.master.moveItemsBetweenReplicaVaults
X
X
Specifies one copy of content on remote site.
wt.fv.master.millisecsToWait
X
Specifies the duration of the delay before the master site resends replica configuration information.
wt.fv.master.siteConfigDeliveryAttempts
X
Specifies the number of times the master site attempts to resend the replica configuration information.
wt.fv.master.replicationThreadCount
X
Specifies the number of threads for replication. You can use this property to optimize replication performance for very large data sets. The default value is 1.
The property wt.fv.master.replicationThreadCount controls the number of threads in thread pool and the entries that can be submitted to the thread pool. The maximum entries in thread pool can be twice the threads in thread pool. The thread pool is designed to process the batch and not an individual item. If the items to be replicated are more than wt.fv.revaultQuerySize (default value 1000), then improvement can be seen after increasing number of threads.
* 
The wt.fv.replicationFileSizeThreshold property may not appear in the file, but it nonetheless exists and is effective. For an explanation of this property, see Replication and Windchill Visualization Service.