DPM Site to Site Replication is getting failed

Forum: Data Protection Manager
Viewing 2 posts - 1 through 2 (of 2 total)
  • #216167


    I”m using DPM 2012 SP 1.

    there are 2 two site. Primary & Secondary .

    my requirement is Sync Primary site protected servers with Secondary DPM Server.

    but every time it is getting failed with below error message.

    ” Affected area:    DPM-PRI\MSDPM2012\msdb
    Occurred since:    9/28/2013 1:14:17 PM
    Description:    The replica of SQL Server 2008 database DPM-PRI\MSDPM2012\msdb on DPM-PRI.hel.ad 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)
        The DPM service was unable to communicate with the protection agent on DPM-PRI.hel.ad (ID 52 Details: The semaphore timeout period has expired (0x80070079))
        More information
    Recommended action:    
    1) Restart the DPM Replication Agent service on DPM-PRI.hel.ad.
    2) If DPM-PRI.hel.ad is configured using certificates, ensure that the DPM CPWrapper service is running on DPM Server and DPM-PRI.hel.ad. Also ensure that certificates used by both the computers are valid.
        Synchronize with consistency check.
        Run a synchronization job with consistency check…
    Resolution:    To dismiss the alert, click below
        Inactivate “

    can you guide me on this.




    Søren Kjærhus


    Try and remove the DB from the PG on the secondary server and the re-add it and then run a new consistency check (It will start that automatically when re-adding to the PG)

    With a bit of luck that fixes your issue, I’m having some of the same issues right now and this was a workaround supplied by Premier support.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.