Property
|
Description
|
wt.fv.CCSUpload.NumOfQueues
|
Specifies the number of processing queues to share that are created and used for retrieving content. The queues dedicated to retrieving content from the remote sites and sending it to the master site are shared among all the replication sessions. Each queue retrieves one content file at a time The default number of queues is 1. Increasing this value increases the number of the processing queues dedicated to retrieving content.
|
wt.fv.sync.disableCreateScheduleAtStartup
|
If set to true, this property disables the creation of a synchronization schedule at startup. The default setting is false, which ensures that a file synchronization schedule exists upon initial startup.
|
wt.fv.verbose.properties
|
Determines whether file vault properties are included in the log upon startup. The default setting is false.
|
wt.fv.verbose
|
Specifies whether the system logs information specific to the file vault feature. The default setting is false.
|
wt.fv.read.buffer_size
|
The size of the buffer for uploading files directed to a vault. The default value is 8192 (8 KB).
|
wt.fv.cleanup.buf_size
|
The size of the buffer for file vault cleanup operations. This buffer is used to read the file names of the folder from which unreferenced content files are to be removed. The default value is 10,240 file names (80 KB).
|
wt.fv.log.mountInfoFile
|
The name of the log file for mounting information. The default name is $(wt.logs.dir)\\MountInfo.log.
|
wt.fv.revaultOnChange
|
Determines whether revaulting is performed in the background for the objects changing their domain or life cycle state. The default setting is true.
|
wt.fv.revaultQuerySize
|
Maximum size of the bucket to be used during revaulting processing. Increasing this parameter decreases the time revaulting takes but increases memory use on the method server. Decreasing this parameter decreases the memory use on the method server, but increases the time that it takes to complete revaulting. The default value is 1000.
|
wt.fv.purgeUnreferencedFvItemsInterval
|
Determines the frequency, in days, that unreferenced items are cleaned up. The default value is 1 day
|
wt.fv.purgeUnreferencedFvItemsOlderThan
|
Determines the age, in days, of unreferenced items that are subject to cleanup. The default value is 30 days.
|
wt.fv.purgeUnreferencedMORItemsOlderThan
|
Determines the age, in days, of unreferenced MasteredOnReplicaItems that are subject to cleanup when the sync operation is run. The default value is 30 days and the minimum value is 2 days.
|
wt.fv.purgeUnreferencedFilesOlderThan
|
Determines the age, in days, of unreferenced files that are subject to cleanup when Remove Unreferenced Files is run. The default value is 2 days.
|
wt.fv.forceContentToVault
|
Determines whether a single vault will be used for all content vaulting. The default setting is false. For more information, see the section Forcing Content to.Vault in Managing Revaulting.
|
wt.fv.useFvFileThreshold
|
If set to true, the property wt.fv.fvFileThreshold takes effect.
If set to false, wt.fv.fvFileThreshold has no effect.
|
wt.fv.fvFileThreshold
|
The maximum number of files that each folder that is associated to a vault can hold. The default value is 50,000.
Files are written to a folder until the threshold is reached. At that moment, the folder becomes read-only and the next content file is vaulted to the next folder mounted to the vault.
For more information, see the section Specifying the File Threshold Value.
|
wt.fv.useVaultsForAllContent
|
Sets the system to send all content to the vaults. The default setting is false. If this property is set to true, all content, regardless of whether it is domain-administered, is uploaded to a DefaultTargetForSite vault even if there is no vaulting rule.
For more information, see the section Sending Content to a Vault in Creating Vaulting Rules.
|
wt.router.checkEmptyRouterQueues
|
Specifies whether the system should check for an empty router queue before determining which router queue to add a new entry to. The default setting is true.
If this property is set to true, the system checks for an empty router queue and, if one is found, adds the entry to the empty router queue. If an empty router queue is not found, entries are added to the router queues in turn.
If this property is set to false, new entries are added to each router queue in turn.
|
wt.fv.faultTolerantVaultsMountStatusCheck
|
Determines the read-only settings for cache vault or single master vault, based on the mount status for clustered setup.
When set to true, the cache vault or single master vault is set to read-only if all the mount statuses of the clustered nodes are INVALID.
The default setting is false. In default setting, the system checks if any mount in a clustered setup is VALID and available for check-in.
|
wt.fv.faultTolerantVaultsAutoRestore
|
Automatically removes the read-only flag from cache vault or single master vault in a clustered setup in case of a hardware or network failure.
The default value is true. In the default setting, the auto-restore mechanism periodically checks whether a cache vault or single master vault in a cluster is writable. The auto-restore mechanism works for 1 hour from the time the vault becomes read-only.
When set to false, the cache vault or single master vault is not automatically restored by the system.
|
wt.fv.faultTolerantVaults.autoRestoreAttempts
|
Determines the number of attempts to restore the read-only cache vault automatically. Default value is 12.
|
wt.fv.faultTolerantVaults.autoRestoreInterval
|
Determines the frequency in minutes to restore the read-only cache vault automatically. Default value is 5.
|
wt.fv.faultTolerantVaults.queueName
|
Determines the queue where the Auto Restore Cache Vault job will run. Default value is commonScheduleQueue.
|
![]() |
In the following discussion, the term ‘directory’ is equivalent to a folder in a Windows environment.
|
![]() |
A folder may also be made read-only if there is no storage space left in the folder's underlying file system directory.
|