FSAUtility -pm incorrectly migrating PH that belong to other Volume / AP targets

FSAUtility -pm incorrectly migrating PH that belong to other Volume / AP targets

Article: 100011025
Last Published: 2014-05-19
Ratings: 0 0
Product(s): Enterprise Vault


If within the folder structure under an existing Volume target, subfolders are shared and added as additional Volume targets, by running FSAUtility –pm to migrate all Archives under the top level volume target, FSAUtility may migrate placeholders for files that were archived under a different Volume target or Archive Point.

This can occur whether the shared subfolder is set at a mount point or just a  regular folder within the existing path structure under the top level Volume target.


FSAUtility does  not detect that the subfolders under the Volume being processed are configured under a different Volume and Archive Point and continue to process them as regular folders under the top level Volume specified with the syntax.


The migration may be completed successfully if performed in the correct order.

If the migration is executed in steps, starting from the Volume target that represents the lowest path in the folder structure, then progressing upwards with individual migration jobs, it would ensure that the Archives from each Volume target are processed correctly before the other Archives within Volume targets higher up in the folder structure are processed.

It is recommendable to test the procedure first before migrating production data.


This issue has been addressed in the following release:

Enterprise Vault 10.0.4 Cumulative Hotfix 3 Release

Enterprise Vault 11.0 0 Release Details




Etrack : 3339458

Was this content helpful?