[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/ 

[SOLVED]: Primary Master Hard Disk Error. Reboot and select proper boot device or insert boot media in selected boot device and press key.

My server was unable to boot from hard disk (it was impossible to choose that disk drive as a boot option in BIOS). The solution was to change SATA settings:
I set "Configure SATA#1 as" to "[AHCI]" and "AHCI CodeBase" to " [Intel AHCI ROM]".
(instead of "SATA#1 Configuration [Enhanced] / Configure SATA#1 as [IDE]" which did not work for me)

#Supermicro Primary Master Hard Disk Error
#Primary Master Hard Disk Error
#Secondary Master Hard Disk Error
#Supermicro BIOS can see disk drive, but can't boot from it
#Supermicro BIOS can't see the disk as boot option  

[SOLVED]: Debian/Ubuntu number of packages for different architectures (arm64 vs amd64)

Summary:

Number of packages for Ubuntu Jammy (22.04) AMD64 = 67626

Number of packages for Ubuntu Jammy (22.04) ARM64 = 65776 (97%)

(this includes basic repositories, such as main, multiverse, restricted, universe)

----

How did I count it:

# amd64

for line in `curl -s http://archive.ubuntu.com/ubuntu/dists/jammy/Release | grep "Packages$" | grep -i amd64 | awk '{print $3}' | sort | uniq`;

do

        echo -n "$line";

        #echo "http://archive.ubuntu.com/ubuntu/dists/jammy/${line}.gz"

        curl -s "http://archive.ubuntu.com/ubuntu/dists/jammy/${line}.gz" |zcat | grep "Package:" | wc -l

done

# arm64

for line in `curl -s http://archive.ubuntu.com/ubuntu/dists/jammy/Release | grep "Packages$" | grep -i arm64 | awk '{print $3}' | sort | uniq`;

do

        echo -n  "$line";

        #echo "http://ports.ubuntu.com/dists/jammy/${line}.gz"

        curl -s "http://ports.ubuntu.com/dists/jammy/${line}.gz" |zcat | grep "Package:" | wc -l

done

[SOLVED] fetch-macos.py 10.15 10.14 catalina

fetch-macos.py utility requires the version of MacOS to be specified within the mysterious format of "Product ID (as seen in SoftwareUpdate)". Hmm... it took me a while to discover those Product IDs.

They are as follows (you need to use string like "001-57224" as an argument to -p option):

# ProductID Version Build Post Date Title 1 001-15219 10.15.5 19F2200 2020-06-15 macOS Catalina
2 001-04366 10.15.4 19E2269 2020-05-04 macOS Catalina
3 071-97382 11.6 20G165 2021-09-17 macOS Big Sur
4 001-36801 10.15.6 19G2021 2020-08-12 macOS Catalina
5 002-23774 12.0.1 21A559 2021-10-25 macOS Monterey
6 002-23589 11.6.1 20G224 2021-10-25 macOS Big Sur
7 061-86291 10.15.3 19D2064 2020-03-23 macOS Catalina
8 041-91758 10.13.6 17G66 2019-10-19 macOS High Sierra
9 041-88800 10.14.4 18E2034 2019-10-23 macOS Mojave
10 001-68446 10.15.7 19H15 2020-11-11 macOS Catalina
11 061-26589 10.14.6 18G103 2019-10-14 macOS Mojave
12 001-51042 10.15.7 19H2 2020-09-24 macOS Catalina
13 071-72781 11.5.1 20G80 2021-07-26 macOS Big Sur
14 001-57224 10.15.7 19H4 2020-10-27 macOS Catalina
15 041-90855 10.13.5 17F66a 2019-10-23 Install macOS High Sierra Beta
16 061-26578 10.14.5 18F2059 2019-10-14 macOS Mojave
17 071-78704 11.5.2 20G95 2021-08-18 macOS Big Sur
18 001-36735 10.15.6 19G2006 2020-08-06 macOS Catalina

So the final version of the wanted command could be:
$ python3 fetch-macos.py -p 001-57224
P.S. You're also might be interested in installinstallmacos.py instead of fetch-macos.py.

[Решено] Boot Camp: "Не удается установить ПО, так как обновление недоступно через сервер Обновления ПО."

    Если вы столкнулись с сообщением "Не удается установить ПО, так как обновление недоступно через сервер Обновления ПО." от Ассистент Boot Camp (при загрузке драйверов для Windows для вашего Mac: "Меню - Действие - Загрузить ПО поддержки Windows"), то у вас есть, как минимум, два варианта:

1. Использовать утилиту brigadier
Качаете, распаковываете, открываете терминал (term) в Launchpad, 
python2.7 brigadier -o /Volumes/ФЛЕШКА/ 

итд

2. Необходимо просто ещё несколько раз нажать на эту же кнопку! У меня сработало примерно через час после первой попытки.

или на английском

[Решено] The application «BV_20171121» can't be opened. Не удается открыть программу «BV_20171121». Unable.

Ошибка возникает из-за архиватора. Попробуйте распаковать архив с программой через утилиту Unarchiver. Мне помогло. Удачи!