My experience with the vault filestore validation has shown me that I don't necessarily get what I desired. For example, I have a vault that somehow is missing its filestore. When I look at that vault in the ADMS console, I see that there are 0/xxxx files in the filestore. If I know of a copy of the filestore somewhere and copy it into the proper location, I find that running the filestore validation does not in fact validate that the files are now in the filestore. It appears that the filestore validation looks at the vault statistics, sees that no files were previously validated, and so simply responds that there are still the same number of files validated. It would be desirable to have the filestore validation confirm whether there are now the correct files in the filestore.
I understand that I can detach the vault and reattach it to affirm that the files are in the filestore, but isn't that what the filestore validation should have done when it was run? And, reattaching the vault now forces me to go back into the user or group accounts and re-associate the vault with those users/groups.
Thank you for your consideration of this suggestion,
Mark Cloyed
IMAGINiT Technologies
