none
DPM 2010- Backing up SQL server "replica is inconsistent" immediately reverts to same state after consistency check RRS feed

  • Question

  • The below is a lot I know, trying to be as detailed as possible to help you out! Thanks for your time!!

    I have DPM 2010 on server "files" I have created a protection group that includes 2 servers. Resources are:

    Server A:
            C:\users\Administrator\Contacts (just to test)
    SQL sources: 
       MEDB\DB
       MEDB\DBTST
       and many more

    Server B:
    2 local folders

    When I setup the group at first everything looked great, it created everything and the protection status went to OK, after not long (I went about my business) I checked on it and all the SQL DBs on SERVER A were "replica is inconsistent" I can right click and Preform Consistency Check which will work, and then indicate OK status for approx 1 second, and then immediately revert to the previous state.

    Under the monitoring tab I get: (summarized)
    The VSS application write of the VSS provider is in a bad state. Ether it was in a bad state or it entered a bad state during the current operation. 0x800423f4
    More info takes me to
    http://technet.microsoft.com/en-us/library/ff399642.aspx 
    Ensure that the required licenses are installed on the server, and then retry the backup. - I didn't have our licenses installed in the Management Tab previously, so I went in and added the number we'd purchased which is now reflected up in the DPM licenses section. Strangely the "in use" under both standard and Enterprise is only 1 (is that correctly indicating I have 1 DPM server or should it reflect that I am trying to backup 2 sources?)

    When I start the consistency check the following logs are created in even viewer

     

    1)

    A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error.  If the backup process is retried,

    the error is likely to reoccur.

    . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. 

     

    Operation:

       PrepareForSnapshot Event

     

    Context:

       Execution Context: Writer

       Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

       Writer Name: SqlServerWriter

       Writer Instance Name: SQL Server 2005:SQLWriter

       Writer Instance ID: {e4492ef3-f865-4ecd-9dd2-3e670304069a}

       Command Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"

       Process ID: 1744

     

     

    A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error.  If the backup process is retried,

    the error is likely to reoccur.

    . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. 

     

    Operation:

       PrepareForSnapshot Event

     

    Context:

       Execution Context: Writer

       Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

       Writer Name: SqlServerWriter

       Writer Instance Name: SQL Server 2005:SQLWriter

       Writer Instance ID: {e4492ef3-f865-4ecd-9dd2-3e670304069a}

       Command Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"

       Process ID: 1744

     

    2)

    SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=1744. Thread=2576. Client. Instance=. VD=Global\{57364C35-3B75-44A4-BF24-A4D669C2F14C}1_SQLVDIMemoryName_0. 

    3)
     Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013

    Error state: 1, Severity: 16

    Source: Microsoft SQL Native Client

    Error message: BACKUP DATABASE is terminating abnormally.

    SQLSTATE: 42000, Native Error: 3201

    Error state: 7, Severity: 16

    Source: Microsoft SQL Native Client

    Error message: Cannot open backup device '{57364C35-3B75-44A4-BF24-A4D669C2F14C}1'. Operating system error 0x80770006(error not found).

    4)
     BACKUP failed to complete the command BACKUP DATABASE ACCESS_CUSTOMER_DATABASE. Check the backup application log for detailed messages.
    5)
    Cannot open backup device '{57364C35-3B75-44A4-BF24-A4D669C2F14C}1'. Operating system error 0x80770006(error not found). 
    6)
     
    SQLVDI: Loc=SVDS::Cleanup. Desc=Close(channel). ErrorCode=(6)The handle is invalid.
    . Process=2304. Thread=2608. Server. Instance=MSSQLSERVER. VD=. 
    SQLVDI: Loc=SVDS::Cleanup. Desc=Close(channel). ErrorCode=(6)The handle is invalid.
    . Process=2304. Thread=2608. Server. Instance=MSSQLSERVER. VD=. 
    7)
    SQLVDI: Loc=SVDS::Cleanup. Desc=Close(channel). ErrorCode=(6)The handle is invalid.
    . Process=2304. Thread=2608. Server. Instance=MSSQLSERVER. VD=Global\{57364C35-3B75-44A4-BF24-A4D669C2F14C}1_SQLVDIMemoryName_0. 
    Wednesday, April 27, 2011 4:54 AM

All replies

  • Hi Zabaat1,

    Was this issue fixed?


    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Wednesday, December 28, 2011 9:07 PM
  • Hi Zabaat1,

    Please go to the protected server and check if SQL VSS service are running.

    open elevated command prompt and write "vssadmin list writers" and check the status of all are "stable" if not then please restart the server and re-run this command again.

    Hope that helps,

    Laith.

    ______________________________________________

    If you found this helpful please mark it as an Answer.

    Thursday, December 29, 2011 8:54 AM
  • Hi

    Just reboot your server and again do the activity which you are performing right now.


    Thanks and Regards Deepak

    Monday, September 3, 2012 9:54 AM
  • Hi

    Just reboot your server and again do the activity which you are performing right now.


    Thanks and Regards Deepak

    Monday, September 3, 2012 9:54 AM