Community

Dear Community, As we transition to Veeam 13 I may be getting a bit lost on the usage/purpose of the above Appliance.I have deployed the VSA ver 13 as in-house demo to explore the features and usage. I also deployed the Veeam Hardened Repository 2.0.0.8 and I like how it makes things easier.However the Usage of the Veeam Infrastructure Appliance which can also be used to deploy the Linux VHR has other roles/features that may not be clear on how they plug-in to the entire deployment. I am reading this part https://helpcenter.veeam.com/docs/vbr/userguide/linux_infrastructure_appliance_byb.html?ver=13 and I would like to understand which components that we used to integrate and configure in VBR ver 12 can be compared. Hope its clear. Though I hope for some more Videos on deployment of the same, on the Veeam Youtube channel on the same with demos.

Hi, We are thrilled to announce the general availability of AsBuiltReport.Veeam.VBR 1.0.0 — a comprehensive PowerShell module that generates professional as-built documentation reports for Veeam Backup & Replication (VBR) infrastructure. What is AsBuiltReport.Veeam.VBR?AsBuiltReport.Veeam.VBR is a specialized report generator that plugs into the AsBuiltReport framework to automatically document your VBR environment. It produces multi-format reports (HTML, Word, Text) that capture the complete state of your backup infrastructure—from backup jobs and repositories to proxies, tape libraries integration, cloud gateways, and more. Key FeaturesReport Sections — Comprehensive coverage of all VBR components including backup repositories, jobs, proxies, WAN accelerators, tape integration, and cloud connectivity Diagram Types — Visual representations of your infrastructure, including backup-to-repository flows, proxy routing, and tape library topology Flexible InfoLevel Configuration — Contr

Hi everyone! I've been working in the lab on some Kubernetes deployments using MobaXterm Home Edition and Rancher. I started off using PuTTY, but found that it could be limiting for what I needed. So I began my hunt to find the best SSH client, and I ended up landing at MobaXterm. In this post, I want to talk a bit about why I opted to use MobaXterm and all of the great features it offers, especially pertaining to working with Kubernetes. Intuitive UI and Easy to NavigateWhile evaluating alternatives to PuTTY, I found that PuTTY along with other SSH terminals looked a bit dated and less approachable. Since this was my first time doing this much terminal-focused Kubernetes work, I wanted a tool I could easily navigate to reduce friction. MobaXterm has a very sleek interface that lends itself nicely to beginners and experts alike. 15 Session Settings/OptionsMobaXterm supports a wide range of session types (SSH, Telnet, RDP, etc.), which makes it useful as a single tool for connecting to

Recently, a customer came to me with what seemed to be a simple question:“Our Veeam Enterprise Manager can suddenly no longer properly connect to the Veeam Backup & Replication server, and the Catalog Service no longer synchronizes. But nothing was changed. What could be the reason?”Ah, the famous IT words: Nothing was changed.Of course, I basically understand what is meant by that. But it does not necessarily mean that a person changed something. Maybe a process, an automation, an update, a migration, etc. changed something. And of course, it is also possible that another person changed something without informing anyone, or that you changed something yourself but do not remember it anymore — or you do not see the impact because, at first glance, it does not seem to have anything to do with the issue.Well then, time to roll up our sleeves and go through the checklist:Was there a Veeam update?No Was there a configuration change in Veeam Backup Enterprise Manager or Veeam Backup &am

Hi everyone,I would like to share a troubleshooting case that took me a few long days to resolve. I hope this can help someone facing a similar issue in the future.The scenario was a VAW deployment to a customer Windows Server.At first, the issue looked like a standard deployment or Windows Installer problem. The Veeam Backup & Replication server was able to reach the target server and upload the MSI package, but the Agent installation never completed.The target server was also a bit unusual: it was heavily used through Remote Desktop sessions, with more than 60 users logged on. Because of that, it was not always easy to know if another MSI installation was really running, and we also had to perform all troubleshooting outside business hours. First issue: another installation already in progressThe first error we saw from the VBR console was:01/06/2026 22:34:43 Failed : [172.16.254.120] Installing package Veeam Agent for Windows Error: Another installation is already in progress. A

I am a first time Veeam customer trying to set up a new test environment using a trial license in hopes to purchase it but unfortunately have had a lot of trouble setting things up and restores have been a nightmare. I have one physical HPE server that is running the Veeam VSA installed from the latest ISO file.  I am able to run a backup of unstructured data but am unable to restore.  When I try I get no mount server is available.  I have a second physical HPE server that is running Windows Server 2022.  I also have a laptop that I’m using just for management with the console installed. The issue is when I go to Backup infrastructure and click on Managed Servers/Microsoft Windows, I see the windows server, we’ll call it backup1.testdomain.com and next to it says “Microsoft Windows server (default Windows mount server).”  When I go to Backup repositories, I see Default Backup Repository and the linux VSA box, we’ll call it VSA1 (not joined to a domain).  If I go to the properties of VS

 Hi everyone,Veeam Advisor v2.0 will be available tomorrow.  For anyone who hasn't come across it before, Veeam Advisor is a free browser-based tool that reads a VBR diagnostic log (VMC.log) and turns it into a health report you can actually read. It covers things like sizing, licensing, configuration reviews, best-practice checks, and a bunch of other useful information.It's a single HTML file, so there's nothing to install, and all analysis happens locally in your browser. What's new in v2.0?@Dynamic Thanks for the suggestion about new color scheme, Ive gone with a more retro game vibe. The biggest addition is a new Resiliency Map.Upload a VMC log and it generates a visual view of your backup environment, showing backup jobs, repositories, and how data moves through backup copy jobs.I originally built it because I wanted an easy way to answer questions like:"Where does this backup actually end up?"or"Do we really have a second copy of everything?"Seeing it as a diagram makes a lot of

Hello,I am planning to upgrade Veeam Backup & Replication from v12.3.2 to v13.0.2 and would like to understand the expected downtime and processing time.Current environment:Veeam Backup & Replication: 12.3.2 Target version: 13.0.2 Local backup repository: approximately 150 TB Repository type: Local repository (Windows) Number of backup jobs: 80 Number of restore points: 2560 (if relevant)I have two questions:How long does the VBR application upgrade itself typically take when upgrading from 12.3.2 to 13.0.2? After the upgrade, how long should I expect any backup chain metadata upgrades or repository upgrades to take for a repository containing approximately 150 TB of backup data?I understand the actual duration depends on hardware performance and repository design, but I would appreciate any real-world experiences or guidance from others who have performed a similar upgrade.Thank you.

If you use Remote Desktop Manager (RDM) with Devolutions Cloud, please take a few minutes to update your installation.Devolutions has identified an issue affecting RDM versions 2026.2.1 through 2026.2.12. Under certain conditions, some entries stored in Devolutions Cloud can become unreadable. While the issue only occurs after a specific set of actions, Devolutions recommends that all organizations running the affected versions install the latest release as soon as possible.Starting July 21, 2026, older affected versions will no longer connect to Devolutions Cloud. This measure helps prevent organizations from encountering the issue.What you should do:Update Remote Desktop Manager to the latest available version. I have verified my Remote Desktop Manager installation and confirmed that it is running version 2026.2.13, which is outside the affected 2026.2.1–2026.2.12 range. Therefore, I cannot show you the update process. But this is very basic and if you are not prompted to update, ple

Even though I am on vacation this week and next still need to keep up with the blog series of 10 in 10 weeks.  For week four we discuss the VSA and operational changes.  You can find a link to my blog and the article below.Blog - Veeam Software Appliance: What Changes Operationally Veeam Software Appliance: What Changes Operationally Introduction The Veeam software appliance is one of the more important operational shifts in the v13 release. It changes the conversation from simply installing backup software to managing a more controlled platform with a tighter lifecycle and a more opinionated security posture.That matters in production because backup teams are often measured by consistency more than flexibility. A platform that reduces configuration drift, narrows the administrative surface, and standardizes maintenance can improve reliability, but it also changes how teams troubleshoot and support the environment. Deployment Changes Traditional deployments often inherit whatever stand

This is the second time my Veeam 13 console cannot connect and shows the error below.The first time I faced this issue, I reinstalled VBR and it worked normally. However, now that I am facing it for the second time, I feel there might be a bug in this version.After checking the Veeam services, I found that there are three services that cannot start:Veeam Backup Server RESTful API Service Veeam Explorers Recovery Service Veeam Web ServiceHas anyone else experienced the same issue?