DPM 2019 Inconsistent Replica

[lmrogers]

Hoping someone can help, been going around in circles.

 

I have a DPM server running backups and mostly all are running fine. I have setup some new Windows 2019 servers and added them to a protection group. Since adding them they have not been able to back up and are constantly giving Inconsistent Replica issues. I have tried running multiple consistency checks but still nothing.

 

The monitoring error is

 

Affected area: RCT\2019 ServerOccurred since: 24/04/2020 10:05:25Description: The replica of Microsoft Hyper-V RCT\2019 Server on 2019 Server.CL-HV.fqdn 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) An unexpected error occurred while the job was running. (ID 104 Details: The filename, directory name, or volume label syntax is incorrect (0x8007007B)) More informationRecommended action: Retry the operation. Synchronize with consistency check. Run a synchronization job with consistency check...Resolution: To dismiss the alert, click below Inactivate

 

If anyone has any tips that would be great!

 

Thanks

[Bruce123]

Hoping someone can help, been going around in circles.

 

I have a DPM server running backups and mostly all are running fine. I have setup some new Windows 2019 servers and added them to a protection group. Since adding them they have not been able to back up and are constantly giving Inconsistent Replica issues. I have tried running multiple consistency checks but still nothing.

 

The monitoring error is

 

Affected area: RCT\2019 ServerOccurred since: 24/04/2020 10:05:25Description: The replica of Microsoft Hyper-V RCT\2019 Server on 2019 Server.CL-HV.fqdn 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) An unexpected error occurred while the job was running. (ID 104 Details: The filename, directory name, or volume label syntax is incorrect (0x8007007B)) More informationRecommended action: Retry the operation. Synchronize with consistency check. Run a synchronization job with consistency check...Resolution: To dismiss the alert, click below Inactivate

 

If anyone has any tips that would be great!

 

Thanks

 

Typical unhelpful message from DPM.

 

What type of backup is this; VM, file, Bare Metal Recover?

 

Have you checked the event log on the target machine? These are often more revealing than those on DPM (as DPM heavily leaverages services / software on the target machine).

 

Also, have you setup AV on the DPM server correctly (to exclude any points for replicas from being scanned/modified)?

 

Thanks,

 

Bruce.