...
| Warning |
|---|
The deduplication policy does not support custom metadata or markers added by users. It means that if this information is added to the copy (primary, secondary) which will not be kept, the data will be lost. As of Verba 9.8.3.8284 custom metadata, markers and labels will be kept, the data will not be lost. (When the primary record is to be deleted and the secondary record is to be promoted to primary the data will be copied over and kept) |
| Warning |
|---|
As of Verba 9.8.3.8284 the deduplication policy will skip and never process again 2N records when the records are under legal hold and/or retention. The only exception is the case when the primary record should be kept and the primary record has legal hold and/or retention, the secondary record should be deleted and the secondary record does not have legal hold or retention applied. If you want to execute a deduplication policy on a skipped record (due to legal hold and/or retention) you need to configure a new deduplication policy to do so. |
| Warning |
|---|
The clock of the Recording Servers must be synchronized, a maximum of 5 seconds drift is allowed for 2N correlation. If the record is under retention (e.g. on WORM storage), the policy will skip the deduplication for the record. |
...