Externalize and/or recall jobs on Web Application profiles may not process all files if site collections have been recently added or deleted from the Web Application. This may be reflected in a completion email that says
"0 of 0 files externalized" or in ULS log entries complaining of "Object reference not set to an instance of an object".

To correct this, try restarting the SharePoint timer server. Using the Services applet under Control Panel | Administrative Tools, stop and restart the Windows SharePoint Services Timer service. Alternatively, from the command line, do a net stop sptimerv3 followed by a net start sptimerv3. Then re-run the externalize or recall job.


Technical Details:

The SharePoint object model that is used in the StoragePoint timer job code sometimes caches the structure of a given web application. If site collections are added or deleted, sometimes the timer jobs will not see these changes because the SharePoint libraries have cached the old structure. This cache is not refreshed until the timer service is restarted.