SQL redirect of Sharepoint data fails with 'error writing file data'

Article:TECH217709  |  Created: 2014-05-22  |  Updated: 2014-05-22  |  Article URL http://www.symantec.com/docs/TECH217709
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


When restoring a Sharepoint SQL database to a SQL instance where there are multiple full and incremental backup sets that must be restored the job may fail with error:


Workaround:  This issue tends to come up when there are 3 or more incremental backups between full backups.  It is recommended to run full backups more frequently so that no more than 2 incremental backups are between fulls.

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.

Supplemental Materials


SQL: SQL redirect of SPSV4 block level incrementals fails with 'error writing file data'


The log scan number (10684:1119:126) passed to log scan in database 'SPSDB1' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.


Article URL http://www.symantec.com/docs/TECH217709

Terms of use for this information are found in Legal Notices