An error may occur if an attempt is made to restore Sharepoint 2010 granular file or document data when the data is stored remote to the Sharepoint content database. The error to occur may be:
V-79-57344-33938 - An error occurred on a query to filegroup ContentDBName\/\SiteName\Shared Documents\Drafts..DocumentName.docx.
WARNING: The file DocumentName.docx was restored from a file that was corrupt when it was backed up, or the backup file is now missing or corrupt. Try restoring the file from another backup, or try repairing the file.
With Sharepoint 2010 it is possible to store file data external to the Sharepoint content database. In these cases, the location within the content database where the file data would normally reside is replaced by pointers to externally stored file data. This is called Remote BLOB Storage (RBS) which is implemented via SQL server. When backing up Sharepoint data with the Backup Exec Sharepoint agent, only the data within the content database is backed up.
Workaround: For RBS enabled content databases, the internal Sharepoint 2010 backup and restore utility should be used along with the supported RBS provider. See http://technet.microsoft.com/en-us/library/ee748649.aspx for more information.
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned in this article. Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns. For information on how to contact Symantec Sales, please see http://www.symantec.com Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.