DPM 2012 SP1 server can't make any System state or BMR backups - volume shares missing on DPM server

Hi everyone.

I have several DPM 2012 SP1 servers in our organisation.

A couple of weeks ago, one of the suddenly stopped being able to perform System state and BMR backups for all the protected servers.

As far as I can see, it's because the DPM server stopped sharing the required volumens used by the Windows backup on the clients (pointing to c:\Program Files\Microsoft System Center 2012\DPM\DPM\Volumes\Replica\Non VSS Datasource Writer etc.).

I have found the following error in the eventlog which might explain why it stopped sharing one of the volumens, but from what I can read, you should never perform a chkdsk on a DPM volume and this is also just one of 4 servers (and therefor 4 shares) that the DPM server performs a System state and BMR backup of, so I can't see that this explains why the other shares are gone.

Volume C:\Program Files\Microsoft System Center 2012\DPM\DPM\Volumes\Replica\Microsoft Hyper-V VSS Writer\vol_a226c724-9add-4126-8af6-5db061eccedf (\Device\HarddiskVolume38) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.

Any good ideas as to how I overcome this problem?

Regards,
Martin

February 20th, 2015 10:51am

And what the exact error are you getting in Alerts tab of DPM console related to this. 
Free Windows Admin Tool Kit Click here and download it now
February 20th, 2015 11:14am

The alert, when I run a Consistency check on the System state or BMR, is the following:

Affected area: Computer\System Protection
Occurred since: 20/02/2015 11:31:08
Description: The replica of System Protection Computer\System Protection on MYSERVER06.mydomain.local 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)
 DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 546, WSB Error Code:  0x1782BE0). (ID 30229 Details: Internal error code: 0x80990ED0)

If I look at the server I try to backup, I can see that Windows Backup tries to start the backup, but fails immediately.

In the eventlog of this server, I have the following error, stating that the remote share is missing.

The backup operation attempted at '?2015?-?02?-?20T10:30:56.309877500Z' has failed to start, error code '2155348081' (The remote shared folder does not exist.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

Regards, Marrin

February 20th, 2015 2:09pm

Hi,

Not sure how the shares got deleted, but easiest way to fix this is to stop protection of the BMR/Systemstate datasources and retain the replica, then re-protect it.  That will maintain the existing recovery points but remake the share so future RP's can be made.   After re-protecting, a CC will be initiated, so do it at a time that will not effect protected server.

Free Windows Admin Tool Kit Click here and download it now
February 20th, 2015 9:09pm

Hi Mike and thank you for your reply.

I've already tried to remove all System state and BMR backups from the protection group (the group contains 4 servers) so that the only thing left in the protection group are the Volumes of the servers and then adding the System states and BMR to the group again.

This however hasn't solved the problem - the System state and BMR backups still can't be run and the errors are still the same.

I've also tried to remove one of the servers System state and BMR backup from one protection group and add it to another - the problem is still the same - the shares are missing and the backup won't run.

Volume backups are running fine and the same is the case for the backup of the SQL 2012 databases on one of the servers as well as the VHD backups of some of the virtual servers (all are running on the same Hyper-V 2012 Failover cluster) so the only thing affected are the System state and BMR backups.

All backups ran fine up to the 6th of February where they began to fail - I've checked the eventlogs of the DPM server and I see nothing out of the ordinary there.

Regards, Martin

February 21st, 2015 12:04am

Hi,

So a "Net Share" command does not list the shares for the bmr backups?  Can you manually make new shares on the DPM server ?

Free Windows Admin Tool Kit Click here and download it now
February 21st, 2015 1:54am

Hi Mike.

NET SHARE reveils the usual shares (C$, IPC$, ADMIN$) and MTATempStore$ and that's all.

I can create new shares without any problems.

Regards, Martin

 

February 21st, 2015 9:37am

Hi,

OK - You may want to check the msdpm*.errlog located in the DPM installation locations Program files\...dpm\temp folder and see if there are any errors attempting to create the shares at time of protection or re-protection.

Free Windows Admin Tool Kit Click here and download it now
February 23rd, 2015 4:50pm

Hi.

The logfiles didn't revien anything related to the missing shares.

But I found a solution that seems to work and that is to remove System state and BMR from the protection groups and then delete the existing replicas.

After that's done, I could add the System state and BMR to the protection groups and then the shares was recreated.

So the only thing I "lost" was the old replicas but that's something that I can do without if this means that I'm able to make new System state and BMR backups.

Regards, Martin

February 25th, 2015 11:26am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics