DPM Site to Site Replication is getting failed RRS feed

  • Question

  • 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.



    Regards, COMDINI

    Saturday, September 28, 2013 2:08 PM

All replies

  • Is that the only error you're getting? I assume you're getting this on the secondary server?

    From the error it's simply indicating that there was an issue with the backup of the MSDPM2012\msdb database on DPM-PRI, which doesn't on its own indicate an issue with site to site replication. Have you tried right running a consistency check on that backup? If so what happens, and if there is a different error afterward what is it?

    To sync backups from one DPM instance you simply navigate to the other DPM server (note if properly configured it should show in the available members list with a DPM icon rather than standard server icon), drill into Protected Servers, then the servers you want to create replica backups of, and finally those items you want to backup. Eg, just like you would for a normal backup, but rather than backing up the data direct you're backing it up from the primary DPM server.

    Saturday, September 28, 2013 8:27 PM
  • Hi Keith, You are correct. Error shows in secondary DPM. Earlier also I did constency check also. But no luck,

    Regards, COMDINI

    Sunday, September 29, 2013 6:40 AM
  • So when you did the consistency check earlier, was the error the exact same one as above, or was it a different one? Quite often the error generated from a consistency check will give more relevant information about the actual problem than the scheduled sync job error.
    Sunday, September 29, 2013 8:51 AM
  • yes. Keith same Error. 

    Regards, COMDINI

    Sunday, September 29, 2013 11:14 AM
  • In that case the first thing I'd try is to remove that backup from the protection group (but don't delete the replica), and then add it again. If something has changed with the main backup that's causing the error this should refresh it, and hopefully get it working again.
    Sunday, September 29, 2013 11:37 AM