Before beginning troubleshooting, it is often a good strategy to start with a single affected file exhibiting such behavior.
- Upload a new file to a document library within the scope of one of the affected profiles.
- When the file is uploaded, open the StoragePoint details menu for that item and review its current location. If the profile was asynchronous, it should show SYSTEM CACHE.
- Run the StoragePoint Content Migration job from the StoragePoint General Settings page and wait for the job to complete.
- Check the StoragePoint Details for the same document to review if it has been moved to the appropriate endpoint.
If the file successfully moved to the endpoint, then we know only older documents are affected.
- Keep in mind that BLOBs may reside in the System Cache for up to the Profile Retention (default of 30 days) even after being copied to the appropriate endpoint.
- If the documents stuck in the cache are younger than the profile retention, then there may not be any problem. Retention can be reduced and the Unused BLOB Cleanup can be run with greater frequency to target files that have already been migrated.
- If the BLOBs are older than the profile retention and the Unused BLOB Cleanup has been running regularly, then they may have been created by SharePoint without being successfully identified by StoragePoint for migration (uploaded by a 3rd party application or PowerShell), follow the steps for "If the file did not move to the endpoint" to resolve the issue.
If the file did not move to the endpoint, take the following steps:
- Verify the Content Migration job is running without error. If it is encountering errors (will be present in the SharePoint ULS logs), check related Knowledge Base articles or contact Metalogix Support for further assistance.
- In Application Management > Storage Profiles > Jobs, run the BLOB Health Analyzer and the Unused BLOB Cleanup jobs for each Storage profile.
- Re-run the Content Migration job and see if the BLOBs are moved.
If the document still has not moved, re-open the StoragePoint Details and manually click the Recall button to push the individual document back into the content database. When this completes click the Externalize button to upload the file directly to its appropriate endpoint (skipping the System Cache). This step will often show any significant errors preventing the Content Migrator from working correctly.
If a root cause can not be determined, another additional maintenance that should be performed to try to resolve the issue is to recycle the Storage Profile to reapply the StoragePoint event receivers and features.
NOTE: This includes an IISRESET.
- In Application Management > Storage Profiles, open each profile and set Externalize content BLOBs to NO, then save it.
- Open each profile and change Externalize content BLOBs back to YES and save it again.
- On each WFE server, perform an IISRESET and restart the SharePoint Timer service.
- Repeat steps under "If the file did not move to the endpoint".