DPM 2016 New install issues

[azureusnation]

Evening All,

 

Having a few issues with DPM at the moment backing up servers.

 

I currently have two servers that no matter what I try or do always have a inconsistent replica on their D drive. Its starting to make me go crazy as we moved from Backup Exec to this thinking it would be an upgrade and a darn lot cheaper with also getting the whole system centre suite for the same cost.

 

Both servers are 2012 R2 except DPM server on 2016 and have the latest agent installed along with windows backup. All of the VSS Writers never error and when I run a manual backup on the server with wbadmin from command prompt it all works fine.

 

Their coming up after a consistency check stating it has completed with an unexpected error of the following:

An unexpected error occurred while the job was running. (ID 104 Details: Cannot create a file when that file already exists (0x800700B7))

 

I've googled and googled and fine no one with this issue nor a solution.

 

Any help will be greatly appreciated.

 

Thanks

 

Ashley

[Killer_Bot]

I've used DPM 2012 and 2016 and, unfortunately, it's never been trouble free or reliable. Not really what you want from a backup solution however sometimes needs must.

 

I encountered quite a few different issues and for some weird reason doing this fixed a few. No idea if it will fix yours but worth a try;

 

Create a Folder called 'DO NOT DELETE' at the root of each drive and in the protection group configure that folder as an exemption to the backup.

 

I have absolutely no idea why that ever worked but it's something I came across when researching one of 'many' errors and it resolved quite a bunch. Just had a quick Google and seen this too but I'm assuming you've already had a search and would likely have said if this resolved.

 

Troubleshooting error: (ID 112 Details: Cannot create a file when that file already exists (0x800700B7)) – Microsoft System Center Data Protection Manager 2012

 

As an aside; we've now moved on to Veeam Backup and Replication Essentials which, whilst it isn't free, is a far superior product in my limited experience with it.

[azureusnation]

Well after another 29 hours, got this message from the job of one of the servers:

Type: Consistency check

Status: Completed

Description: The job completed successfully with the following warning:

An unexpected error occurred while the job was running. (ID 104 Details: Cannot create a file when that file already exists (0x800700B7))

More information

End time: 11/10/2017 18:48:11

Start time: 10/10/2017 13:11:02

Time elapsed: 29:37:08

Data transferred: 91,417.04 MB

Cluster node -

Source details: D:\

Protection group members: 1

Details

Protection group: REDACTED

Items scanned: 585683

Items fixed: 121972

 

This is soo annoying... And as soon as I try to do a Syncronization:

Type: Synchronization

Status: Failed

Description: The replica of Volume D:\ on REDACTED is not consistent with the protected data source. (ID 91)

More information

End time: 11/10/2017 18:55:41

Start time: 11/10/2017 18:55:34

Time elapsed: 00:00:06

Data transferred: 0 MB

Cluster node -

Source details: D:\

Protection group members: 1

Details

Protection group: REDACTED

Edited October 11, 2017 by azureusnation

[azureusnation]

Progress Update

 

I did come across an artical online this morning regarding the issues im facing and it may help you in the future as well:

https://social.technet.microsoft.com/Forums/en-US/7737e9b6-f5f3-4fbe-a9a3-0fdb3e134713/dpm-2016-ur2-files-fail-to-synchronize-but-log-file-is-empty?forum=dataprotectionmanager

 

We run deduplication on the servers that are having issues and only just thought about this this morning. Sure enough Microsoft have admitted there is a bug with scdpm and deduplicated volumes that for us in DPM 2016 will be fixed in UR4... when ever that will be. There is also an update going to be published for 2012R2 DPM.

 

I'll let you know how i get on with un deduplicating a server to see if that fixes the issues.