Actually i know exactly who in support wrote that Powershell script in support, so i would definitely open up a case and get a copy of it and they will help you through what you need to do
We had a similar problem, and spotted the potiental for data loss with fsautility
Read up a fair bit on it, and people suggested using virus scanners to scan a share, and in doing so, the scanner would resolve all current placeholders. I didnt like the sound of this personally (we already had a Symantec anti-virus configured to play nice with EV, so didnt want to remove that, install another, reconfig etc etc)
What I did in the end was put together a pretty simple PowerShell command, that recursively searches through a provided path, and them attempts to read the first line from any archived files it finds - and in doing so recalls it.
Heres the basis of it:
ls <path> -rec | where{$_.attributes -match "Offline"} | gc -totalcount 1 > $null
Can go through the in's and out's of it, but basically, it loops through the entire folder structure (much like dir /s), finds any files with the archive bit set, and then attempts to read the first line (redirecting the output to null, as we're not really interested in it!)
Possibly goes without saying, but disable the share for archiving, and you'll need the reg change 'ByPassRecallLimitsForAdmins'
Another pair of commands along the lines of the above:
ls <path> -rec | where{$_.attributes -match "Offline"} | measure-object
Returns the number of placeholders in a path. And:
ls <path> -rec | where{$_.attributes -match "Offline"} | select -first 100 | gc -totalcount 1 > $null
Does a bit more of a controlled recall, by just doing the first 100 placeholders it finds.
Can expand on anything, or may delete post if its a complete red herring - let me know
Ian
