Protecting SQL databases in Lync 2013 with DPM 2012 R2

I am repeatedly having trouble getting SQL databases of Lync consistent.

We have been backing up our lync 2013 servers for quite some time (several months) via SC DPM 2012 R2 . I am backing up the root drive, as well as all the SQL databases for full protection. It worked fine up until December when the replica's went inconsistent. 

I have tried:

1. Performing a consistency check
2. Moving Servers to a new Protection Group to restart with fresh replicas
3. Moving to new group while also deleting old replica data
4. REmoving DPM client and starting from scratch with protection lync server

Nothing seems to work to get them back in proper order and they go inconsistent after a couple hours again. WE have 4 total lync servers and all are running into the same issue

Below is a sample log from one of the inconsistent databases

Affected area:<SERVER>\RTCLOCAL\master
Occurred since:12/22/2014 2:18:49 PM
Description:The replica of SQL Server 2012 database LYNC2013EDGE\RTCLOCAL\master on <SERVER>.domain 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 VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111 Details: VssError:The specified object was not found.
 (0x80042308))
More information
Recommended action:Please check that the Event Service, the VSS service and the shadow copy provider service is running, and check for errors associated with these services in the Application Event Log on the server <server>.domain. Please allow 10 minutes for VSS to repair itself and then retry the operation.
For more information on this error, go to http://go.microsoft.com/fwlink/?LinkId=132612.
Synchronize with consistency check.
Run a synchronization job with consistency check...
Resolution:To dismiss the alert, click below
Inactivate

Any advice would be greatly appreciated