StoragePoint Version: 4.2.0.1300 Legacy data needs to be recalled back to the content DB due to a business decision to move the information from externalized blobs back to the content DB.
The recall blob is not showing, as scheduled jobs, but in the sharepoint jobs definitions it shows but no as an executable job. Just the definition of the job itself.
To execute a recall blob back to the content database is its important to have enough free space for the database to grow back to and also the sharepoint servers from where the recall blobs jobs is going to run has to have enough space in the main c:\ drive in order to perform the action. If not, the operation will not run on the server specified for running the recall job. It will only shows as a define action to be performed and no other recall blob can be executed until this shows.
This case will not show the jobs running not even in the jobs menu.
Delete any job recall job that is running or it is define and all associated jobs definitions.
1. to do so go to central administration > Monitoring > Review Jobs Definitions
2. Sort the result by the title column, find the Job(s) that are called "StoragePoint Recall".
3. Delete all the Jobs.
Check for Disc Drive space on the servers used to run the recall job. If almost full increase the space of the disk or delete/remove files to the unit drive.
4. Restart all Sharepoint Timer Jobs on the WFE servers.
5. Return to Storagepoint Menu and look for the profile where the recall job is to be run on storage profiles click on the jobs options
6. click first on the Analyze and estimate button to have a clear picture of the amount of blobs/files to be recalled. Close and go back to the jobs menu an click on Recall Now.
7. This will generate the recall job to run at that moment.
8. Check the jobs status to see the jobs is running.
9. Also you can check the amount of files recalled by doing again the step 6 to see the progress of the recall.
10. Recall job will finish when the number of externalized files are back to 0.
