Overview of orphaned shortcut deletion check types in Enterprise Vault
Article ID: 100020274
Updated On:
Resolution
If desired, a Fat Check can be run manually. To do so, add the following registry key to the EV server that processes the mailbox in question.
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
Open the registry on the Enterprise Vault server and set the following key:
HKLM\SOFTWARE\Wow6432Node\KVS\Enterprise Vault\Agents\
Name: OrphanedShortcutCheckType
DWORD - value = 1
0 (default)
EV 12 and higher should use the following setting and remove the above entry:
HKLM\SOFTWARE\Wow6432Node\KVS\Enterprise Vault\Agents\
Name: FixOrphanedShortcut
DWORD - value = 1
0 (default)
Once the registry key has been added a restart of the archiving task must occur to implement the changes. Please refer the the Related articles section for more information.
Note: The next time the archiving task runs with shortcut processing, a Fat Check will be run against the mailbox. If there are a larger number of orphaned shortcuts, it is possible that one pass will not be enough to remove them all. This is due to the fact that the default number of orphaned shortcuts to be processed is 1000.
Issue/Introduction
There are two different types of checks performed to determine if a shortcut is an orphan.
- Fat Check
- Thin Check
A Thin Check runs faster, but can leave some orphaned shortcuts in the mailbox. This is because a Thin Check queries the Vault Store database to determine if there is a deletion record for each item. These records are only maintained throughout the transaction history period, which is by default 32 days. When the age of a deletion record exceeds the transaction history period it is deleted from the Vault Store database. A Thin Check would not consider shortcuts without a deletion record as being orphans, so they are not deleted from the mailbox.
A Fat Check is a more intensive orphaned shortcut check. The Archive Task will confirm that the item is still available on the Enterprise Vault storage location. If the item is not available, it is considered to be orphaned and the shortcut will be removed from the mailbox.
When a Thin or Fat orphaned shortcut check is run on a mailbox, the date and time of the check is recorded. When a scheduled run of the Archive Task occurs, this date and time is compared with the transaction history period defined for the Enterprise Vault site. If the last orphaned shortcut check date and time is older than the transaction history period then a Fat Check is run. If it is younger than the transaction history period, then a Thin Check is run because the deletion records for orphaned items should still be present in the Vault Store database.
