Restore of SQL, SharePoint, or Enterprise Vault data from a block level Incremental or differential fails with 'error writing file data'
|Article:TECH217709|||||Created: 2014-05-22|||||Updated: 2014-12-15|||||Article URL http://www.symantec.com/docs/TECH217709|
Unable to restore from successful SQL, SharePoint, or Enterprise Vault backups that used the block level incremental or differential backup type.
V-79-57344-33938 - An error occurred on a query to database ContentTest.
V-79-57344-33938 - The log scan number (10587:6155:169) passed to log scan in database 'ContentTest' 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.
Backup Exec Remote Agent Debug
"SQL2 INCR: could not write to file: Error = 87".
A hotfix is now available for this issue in the current version(s) of the product(s) mentioned in this article. Refer to the Hotfix link under Related Documents at the end of this article to obtain the hotfix needed to resolve the issue.
Backup Exec 2014 Rev 1786 Hotfix (TECH225092).
This issue is resolved in Backup Exec 2014 or later versions.
To resolve this issue and receive the new Backup Exec improvements please upgrade to the current version of Backup Exec.
NOTE: Symantec continues to focus on the current release and future releases; there are no plans to address this issue by way of a patch or hotfix in earlier versions of the software at the present time. Please contact your Symantec Sales representative or the Symantec Partner for upgrade information including upgrade eligibility to the release containing the resolution for this issue. For information on how to contact Symantec Sales, please see http://www.symantec.com.
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