
- #Backup exec 2010 on server 2016 install#
- #Backup exec 2010 on server 2016 update#
- #Backup exec 2010 on server 2016 software#
#Backup exec 2010 on server 2016 update#
Addendum: The crash might be fixed with update KB4511555 released on August 30, 2019. This article will be updated when 20.5 is available. The fix for this issue will be included in the next release ( 20.5) of Backup Exec.

Open Server Manager, click Tools in the upper-right column and select. The Backup Exec 2010, 2010 R R3 Remote Agent for Windows Systems and NetWare Servers is strongly recommended for use with Backup Exec 2010 R R3 the Backup Exec 12.5 remote agent (with latest service pack) is also compatible for the purpose of rolling upgrades with the exception of any caveats listed in the notes. After it is installed, you can follow the instructions below: 1.
#Backup exec 2010 on server 2016 install#
If you intend to use Windows Server Backup, you have to first install it as a Windows Feature using Server Manager or PowerShell. NET 4.8 through Programs and Features in Control Panel. Windows Server Backup 2019 is essentially the same as Windows Server Backup 2016. NET 4.8 as the cause and recommend uninstalling the update:

The event log contains an error 0xe0434352 for BackupExec.exe, version. This issue is also observed on servers or workstations with the Backup Exec Remote Administration console installed. NET Framework 4.8 on the Backup Exec media server, the Backup Exec console crashes when starting, as shown in the following screenshot. Sebastian writes that there is already a KB article (Backup Exec console crashes after installing. It now runs again – if necessary all BE services have to be restarted net 4.8 bricks BE – the backup can't start anymore after installing the update. Then I got today another German Comment from blog reader Sebastian, reporting the same issue: Auch das alles ohne Fehlermeldungen in der Ereignisanzeige. All this without error messages in the Event Viewer.starten. Associated services all run, can also be stopped and restarted.
#Backup exec 2010 on server 2016 software#
There are no messages regarding the backup software in the Event Viewer. Restarting the server does not solve the problem either. Then I started our backup software BackupExec 15 on one of the servers because I planned to change a setting before the backup tonight.Įrror message "BackupExec does not work anymore". Before that I checked all hints for possible issues with the new updates like every month. To back up Microsoft Exchange Server 2016, you must install Backup Exec on a Microsoft Windows 2012 64-bit server or newer. I just installed the August updates on our Windows Server 2012 R2. Support for Exchange 2010 phased out in Backup Exec 21.3: -Added support for Exchange 2016 CU21: : Backup Exec 21.3. Here is the translation of his German post: contacted me via e-mail and pointed out a big problem. Microsoft states that the update fixes a crash in the Bass Class Library (BCL) that occurs after event logs are broken down. These updates can also be downloaded from Microsoft Update Catalog.

The colleagues of Deskmodder took it up here and published the following list of cumulative updates for various Windows versions. But Microsoft has probably added to the 20.8. Already on Augthere was an update, as mentioned in the German comments here (and this article).
