none
The replica of SQL Server 2005 database is inconsistent with the protected data source. RRS feed

  • Question

  • Hi,

     

    I'm running DPM 2007 SP1 on Server 2008 R2. I have Protectoin Groups working for a number of machines, however I'm having problems backing up a CRM database on one machine (Server1). This server is running Server 2008 with SQL 2005 64 Bit. Server1 also runs a SharePoint farm which I have no issues protecting.

    WHenever I try to sycn the CRM Db I get a message saying:

    The replica of SQL Server 2005 database Server1\MyCompany_CRM on Server1.headoffice.mycompany is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent.

    For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)

    Retry the operation.

    Run a synchronization job with consistency check...Synchronize with consistency check.

     

    Despite running numerous synchronization they always fail.

    I have tried creating a new protection group but with just the CRM db but still encounter the same issues.

     

    Thanks,

    Adam

     

    • Moved by MarcReynolds Friday, March 4, 2011 1:25 PM (From:Data Protection Manager)
    Wednesday, February 23, 2011 8:23 PM

Answers

  • Okay, the only message there that would concern me is the login failure.  Is that specific to the CRM database and does that get logged only when you try to run a CC?

    I think the next steps here would be to run the consistency check and watch the log files on both the SharePoint and DPM servers:  Program Files\DPM Installation Folder\DPM\Temp

    Sort them by time date and then try the CC.  Look at what files are updated and open each and search for CRM to see what we are logging about that database.  You can pull them into Excel and when you find something about the CRM database that is failing, filter on the ThreadID related to that line and post those in here for us.  We may be able to get something from those.


    Thanks, Chris Butcher - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Thursday, March 17, 2011 2:49 PM
    Moderator

All replies

  • Hi Adam,

    Any clues in the SQL server eventlog or vssadmin list writers command output?


    My DPM blog ystartsev.wordpress.com
    Thursday, February 24, 2011 10:03 AM
    Moderator
  • Hi Yegor,

    Thanks for your reply.

    There is nothing in the event log on either the DPM server logs or the machine which houses the CRM database which I'm attempting to protect. No errors either when I ran vssadmin list writers.

    Output from CRM host.

     [Version 6.0.6002]
    Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

    C:\Users\tss>vssadmin list writers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {7820a722-0158-43a8-8660-9f96efb96a0e}
       State: [1] Stable
       Last error: No error

    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {25360e59-462c-4d9f-8d4f-bd6ae5899945}
       State: [1] Stable
       Last error: No error

    Writer name: 'SharePoint Services Writer'
       Writer Id: {c2f52614-5e53-4858-a589-38eeb25c6184}
       Writer Instance Id: {b48ad90e-43f7-4dc5-a0b7-a188a3a5f40f}
       State: [1] Stable
       Last error: No error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {2ac391b2-06df-4005-bcea-566a2e383aa0}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {070248b1-ae9f-480a-a7a2-7dece42c6b4f}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {a305de00-8d3b-476a-a8d9-0f36a3e3045a}
       State: [1] Stable
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {1381828e-f3d9-4c0a-8a9e-d9ad0ebe9302}
       State: [1] Stable
       Last error: No error

    Writer name: 'OSearch VSS Writer'
       Writer Id: {8d5f38cd-fb7a-49ca-ae1b-21d1f017d8f9}
       Writer Instance Id: {85bccbd2-696d-41f5-b132-bb69725d5ac6}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {5befc213-02f7-4bd7-8f17-c698a8cfa4fb}
       State: [1] Stable
       Last error: No error

    Writer name: 'SPSearch VSS Writer'
       Writer Id: {57af97e4-4a76-4ace-a756-d11e8f0294c7}
       Writer Instance Id: {2a4565bc-054a-48e8-ac60-a14eab90d074}
       State: [1] Stable
       Last error: No error

    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {a34e1f5a-a4d7-4c9e-ad76-d823ed2c75e3}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {bd21892e-c111-46a4-9639-5f11c12eb9a2}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {e9d8512f-5777-4c1d-9c30-441ea15a4f7c}
       State: [1] Stable
       Last error: No error

    Thanks,

    Adam

    Thursday, February 24, 2011 7:55 PM
  • Adam,

    It appears that you have SQL and SharePoint all running on the same box.  I would assume that the CRM is part of a different instance than the SharePoint databases (although that won't necessarily affect the issue).  Since SharePoint protection is working fine, we can assume that both the SharePoint and SQL writers are running fine.

    In order to get to the bottom of this, I would try to put the database in its own protection group and then look at the monitoring tab for the job and find the "initial replication" job.  My guess is that is failing and thus any subsequent syncs or express fulls will also fail.  If you can see the failure for that, it may give us more information as to what is going on.


    Thanks, Chris Butcher - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Tuesday, March 8, 2011 3:55 PM
    Moderator
  • Hi Chris,

     

    Thanks for your reply. I had previously created a protection group containing just the CRM DB and ran into the same errors as you have suggested.

     

    Below are the logged events from Event Viewer on the server hosting the CRM database.

    Event ID 18264


    Database backed up. Database: MyCompany_CRM, creation date(time): 2010/12/19(13:57:41), pages dumped: 1, first LSN: 56158:16:116, last LSN: 56158:65:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3F0B646B-4D3E-4E08-80FE-E48F73EE30A3}1'}). This is an informational message only. No user action is required.

     

    Event ID 3198

    I/O was resumed on database MyCompany_CRM. No user action is required.

     

    Event ID 3197

    I/O is frozen on database MyCompany_CRM. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.


    Event ID 18456

    Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]

     

    Thanks,

    Adam

     

    Wednesday, March 16, 2011 9:22 PM
  • Okay, the only message there that would concern me is the login failure.  Is that specific to the CRM database and does that get logged only when you try to run a CC?

    I think the next steps here would be to run the consistency check and watch the log files on both the SharePoint and DPM servers:  Program Files\DPM Installation Folder\DPM\Temp

    Sort them by time date and then try the CC.  Look at what files are updated and open each and search for CRM to see what we are logging about that database.  You can pull them into Excel and when you find something about the CRM database that is failing, filter on the ThreadID related to that line and post those in here for us.  We may be able to get something from those.


    Thanks, Chris Butcher - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Thursday, March 17, 2011 2:49 PM
    Moderator
  • I am hoping that using the above information you were able to find the problem and resolve it.  I will go ahead and mark this as answered at this time.  If you are still having problems with this, pelase reopen the task and provide the information requested above.  Thanks!
    Thanks, Chris Butcher - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Tuesday, April 26, 2011 3:58 PM
    Moderator