none
Intermittent SQLWRITER problem when protecting a SharePoint Farm RRS feed

  • Question

  • Hello,

    we've been protecting a SharePoint 2007 Farm since several years ago, and we're suffering intermittent partial failures on the content database backup since a few days. Approximately 60%-70% of the databases are being backed up without error, then a problem arises with the SQLWRITER and the rest of database backups are in failure. Not always the same databases fail, it varies from a recovery point to another.

    In the protected server's application log we can see the typical sequence of information events 3197 (I/O frozen...), then 3198 (I/O was resumed...), then 18264 (Database backed up), then 17137+17573+5084+5084+18625 (all relative to the RollbackSnapshotTempDB{GUID} backup) for the majority of the databases, but from time to time there is a failed one. in this case, after the 17137 event (Starting up database RollbackSnapshot TempDB{GUID}), we get an error event 3415:

    Database 'RollbackSnapshotTempDB{B5CC1382-2367-4F09-A1B2-F8B78BF911D4}' cannot be upgraded because it is read-only or has read-only files. Make the database or files writeable, and rerun recovery.

    , followed by an SQLWRITER error event:

    Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 1813 Error state: 2, Severity: 16 Source: Microsoft SQL Server Native Client 10.0 Error message: Could not open new database 'RollbackSnapshotTempDB{B5CC1382-2367-4F09-A1B2-F8B78BF911D4}'. CREATE DATABASE is aborted. SQLSTATE: 42000, Native Error: 3415 Error state: 3, Severity: 16 Source: Microsoft SQL Server Native Client 10.0 Error message: Database 'RollbackSnapshotTempDB{B5CC1382-2367-4F09-A1B2-F8B78BF911D4}' cannot be upgraded because it is read-only or has read-only files. Make the database or files writeable, and rerun recovery.

    I can't find any reason why the SQLWRITER is failing on this operation, as it happens only on a reduced percentage of databases, and moreover it is DPM who fully manages the creation of this temporary dbs.

    Does anybody have any hint or suggestion in order to get rid of this problem?

    Thanks in advance!! 


    • Edited by Roberto MD Wednesday, June 1, 2016 10:56 AM
    Wednesday, June 1, 2016 10:55 AM