[ Blog ] Veeam #Backup and #Replication 13 released

The wait is over! The long-awaited new #Veeam Backup and Replication 13 is finally GA and available for download.

The number of new features and enhancements is impressive, further solidifying the solution's leadership position in the market for backup solutions.

 
What's new in #Veeam Backup and Replication 13
With tons of new http://rviv.ly/PV4r1S

[ Blog ] Using the #Veeam Deployment Kit

Latest Veeam Backup & Replication v13 introduces the Veeam Deployment Kit, a package used to enable certificate-based authentication.

Once installed on a target server, Veeam leverages the #certificate for authentication instead of the traditional username and password.

The Veeam Deployment Kit can be used to http://rviv.ly/BDnyrt #autenticazione #deploymentkit

[ Blog ] Veeam #Backup for #Microsoft 365 v8.3 available

Veeam recently released the new #Veeam Backup for Microsoft 365 v8.3 with includes enhancements and bug fixes.

After the installation, the Veeam Backup for Microsoft 365 build number will be 8.3.0.2201.

 
Upgrade options
If you already have Veeam Backup for Microsoft 365 installed in your infrastructure, a direct http://rviv.ly/lY8MoV #exchange

[ Blog ] Veeam #Backup and #Replication 13 released

The wait is over! The long-awaited new #Veeam Backup and Replication 13 is finally GA and available for download.

The number of new features and enhancements is impressive, further solidifying the solution's leadership position in the market for backup solutions.

 
What's new in #Veeam Backup and Replication 13
With tons of new http://rviv.ly/PV4r1S

Den heutigen Tag ernenne ich zum Tag des Backups. Gefühlt habe ich mich nur um Backups in verschiedenen Szenarien gekümmert.

1. Windows Server Backup mit #VSS
2. #Veeam für Hyper-V
3. Skript für #restic angepasst
4. Mit #Powershell für einen Updatedienst herumgespielt

#Restore mache ich dann morgen. 😉

#backup

Issues with #Veeam Backup on MS365 accounts, due to EWS retirement in Exchange Online

https://borncity.com/win/2026/04/08/veeam-backup-issue-with-ms-365-mailboxes-due-to-the-ews-transition-in-march-2026/

Sooo, #backrest is not really my thing either. You can't change the connection settings of an existing repository, which means no credential rotation and no clean way to handle IP changes when a server moves. That's a pretty fundamental limitation for a backup solution.

I'll take a closer look at #restic without relying on a frontend.

I'm also skeptical about #Borg #Backup and, more broadly, backup tools built on Python/Ruby/shell stacks. There's a lot of room for subtle breakage without strict type safety, and pushing performance-critical parts down into C/C++/ASM layers doesn't exactly inspire confidence either.

Makes me wonder what enterprise solutions look like under the hood. Apparently #Veeam is C#, which is actually a reasonable choice - but requiring a Windows server (and not being OSS) makes it a non-starter for me.