[SOLVED]: DPM Error (0x800423F4) or DPM (ID 3114) or DPM (ID 30111) VssError:The writer experienced a non-transient error. Or Backup Exec: 0xe000943f - Database s failed to freeze for backup. This can be caused if the database is in a state that does not support backup; such as offline, standby, or recovering.

I got my server backed up by DPM and Backup Exec, thus I had warnings from both backup solutions (error codes/IDs listed below).

At first check output of the command "VSSadmin List writers" 

if you'll see output like this: "Writer name: 'SqlServerWriter' State: [8] Failed Last error: Non-retryable error"

then just reboot your SQL server OS which is used for database in your SharePoint setup.

 

Symptoms :

DPM 2016 (Data Protection manager)

            Recovery point creation jobs for Microsoft Hyper-V xxxyyzz on xxxyyzz have been failing. The number of failed recovery point creation jobs = 1.

            If the data source protected has some dependent data sources (like a SharePoint Farm), then click on the Error Details to view the list of dependent data sources for which recovery point creation failed. (ID 3114)

           

             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 writer experienced a non-transient error.  If the backup process is retried,

            the error is likely to reoccur.

            (0x800423F4))

           

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

 

Backup Exec

            Backup- ConfigurationV5-DB (xxyyzz\xx\SharePoint_Config)V-79-57344-37951 - Database SharePoint_Config has failed to freeze for the snapshot backup.

 

            Job Completion Status

            Job ended: 13 марта 2024 г. at 19:52:20

            Completed status: Failed

            Final error: 0xe000943f - Database s failed to freeze for backup.  This can be caused if the database is in a state that does not support backup; such as offline, standby, or recovering.  

            Final error category: Other Errors

 

            For additional information regarding this error refer to link V-79-57344-37951

[SOLVED]: How to fix DPM 40003 error (Data Protection Manager 2016)

Summary: DPM fails with error 40003 complaining either on DPM agent's or DPM server's storage.
It seems the real reason (in my case) behind this error was that the last backup taken was corrupted!
(Furthermore, in my case it turned out that RAID array was in the degraded state on DPM server's storage side. So it's better for you to CHECK YOUR DISK SUBSYSTEM and RAID STATUS!!! of both client and server). 

To fix it you need to delete last (possibly corrupted) backup (or Recovery Point in terms of DPM).
However you can't do it via GUI, only from Powershell.
Basic concept to do it is as follows:
* Determine Protection group of that RecoveryPoint
* Determine Datasource of that RecoveryPoint
* Determine the last RecoveryPoint available for that Datasource
* Delete it.
This helped me a lot of times (even with degraded RAID!).

Don't forget to launch Powershell with elevated/administrator privileges.

$pg = Get-ProtectionGroup -DPMServerName your_DPM_server | where {$_.Name -eq "MSSQL System Databases" }

Get-Datasource -ProtectionGroup $pg | where {$_.Computer -like "*computer_with_DPM_agent*"  } |where {$_.Name -eq "msdb" }

$ds = Get-Datasource -ProtectionGroup $pg | where {$_.Computer -like "*computer_with_DPM_agent*"  } |where {$_.Name -eq "msdb" }

Get-RecoveryPoint -Datasource $ds |Sort-Object -property BackupTime

Get-RecoveryPoint -Datasource $ds |Sort-Object -property BackupTime |select-object -last 1

$rp = Get-RecoveryPoint -Datasource $ds |Sort-Object -property BackupTime |select-object -last 1

echo $rp

Remove-RecoveryPoint -RecoveryPoint $rp 

Update: I noticed that after rebooting DPM server this error almost gone (while still running with degraded RAID 5!). I guess it's because of hard swapping issues and hence slow disk subsystem due to degraded RAID - it was partially solved by reboot.
So simple reboot of DPM server may also help you!

Original idea taken from here:
[1] https://social.technet.microsoft.com/Forums/en-US/30f8ef3f-1d20-42ae-bffb-dab49fdea0fc/quoterror-40003-the-storage-involving-the-current-operation-could-not-be-read-from-or-written?forum=dataprotectionmanager
[2] https://www.jfe.cloud/how-to-delete-a-specific-recovery-point-in-dpm/