none
Data Protection manager 2013 failed SQL Synchronization RRS feed

  • Question

  •  For some sql  database I got this error

    The replica of SQL Server 2012 database SQL on SQL1 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. 

    I tried consistence checks but it fails 

    The database are 2008 version and some are 2012 version of sql server Enterprise edition


    Monday, August 26, 2013 3:48 AM

All replies

  • Hi

    Need the details of the failed DPM Sync and CC jobs.   Any volsnap or VSS errors in the event log on the protected servers ?


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, August 26, 2013 9:59 PM
    Moderator
  • The volsnap error is 

    The oldest shadow copy of volume C: was deleted to keep disk space usage for shadow copies of volume C: below the user defined limit.

    Affected area:	Computer\System Protection
    Occurred since:	27-08-2013 09:02:33
    Description:	The replica of System Protection Computer\System Protection on file1. 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)
    	DPM is out of disk space for the replica. (ID 58 Details: Internal error code: 0x80990ED2)
    	More information
    Recommended action:	Ensure there are no pending disk threshold alerts active for this data source and rerun the job. DPM may have automatically grown the volume and resolved the alerts.
    	Synchronize with consistency check.
    	Modify Disk Allocation ...
    	Run a synchronization job with consistency check...
    Resolution:	To dismiss the alert, click below
    	Inactivate
    

    And for sql server

    Affected area:	SQL1\Tfs_DefaultCollection2
    Occurred since:	27-08-2013 09:00:00
    Description:	The replica of SQL Server 2012 database SQL1\Tfs_DefaultCollection2 on SQL1. 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)
    	DPM failed the current backup because the previously standalone SQL database is now a part of a SQL Availability Group.
    Database: SQL1\Tfs_DefaultCollection2 (ID 32030 Details: )
    	More information
    Recommended action:	Stop protection of the current standalone SQL Database and reprotect it as a Availability Group database.
    	Synchronize with consistency check.
    	Run a synchronization job with consistency check...
    Resolution:	To dismiss the alert, click below
    	Inactivate
    

    Tuesday, August 27, 2013 3:55 AM
  • Did you figure this out?  Having the same problem.
    Friday, December 6, 2013 10:57 PM
  • Hi Anurag,

    The solutions are in the alerts - Please follow the recommended actions.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Saturday, December 7, 2013 1:14 AM
    Moderator
  • When I try to re-add the DB via the availability group DPM doesn't list any databases when I expand the availability group name.
    Saturday, December 7, 2013 1:21 AM
  • Hi,

    Please make sure dpm agent is on both SQL servers and that the SQL writer is enabled and running on both SQL servers.  Make sure the databases are listed in the output of list writers command from diskshadow.exe.

    1) open an administrative command prompt

    2) run: diskshadow.exe /l output.txt

    3) type:  LIST WRITERS

    4) Type: exit

    4) look in the output.Txt file and make sure the databases are listed under the SQL server writer.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Saturday, December 7, 2013 4:31 PM
    Moderator