Restoring archived content with FSAUtility -t leads to SystemOutOfMemory exception.

Restoring archived content with FSAUtility -t leads to SystemOutOfMemory exception.

Article: 100046770
Last Published: 2020-08-18
Ratings: 0 0
Product(s): Enterprise Vault


When using FSAUtility to restore archived content within a subfolder, the tool may terminate with an exception whilst performing ArchiveFolder path validation. 


Error Message



When FSAUtility -t starts the restore processing, it first walks through the entire set of ArchiveFolder paths following the RooIdentity order for the entire Volume target being processed. The order in which the ArchiveFolders are registered with the corresponding database reference during archiving dictates the incremental order the RootIdentity values are assigned. When FSAUtility starts the ArchiveFolder validation, it follows the RootIdentity order, not an AlphaNumeric order. This means that the actual subfolder defined in the restore syntax would need to wait until the corresponding RootIdentity value is reached and the subfolder can be validated as a match for the restore.

For Enterprise Vault implementations where the archiving Task has already processed millions of subfolders, each with the respective ArchiveFolder record, this ArchiveFolder path validation can take many minutes before the actual items, within the matched subfolder, can be queued for restore.

This logic may lead to the above exception, which terminates the restore job.



This issue was fixed in Enterprise Vault 12.5.1.

Enterprise Vault 12.5.1 is available
Release Date: March 16, 2020
For information about the release click on the following content article:






JIRA : CFT-2307

Was this content helpful?