Community

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

Hi everyone,I'm running into a strange issue with a Veeam Backup & Replication Appliance v13.0.2.29 on a physical HPE Gen10 server with iLO 5 (firmware 3.13).The appliance boots normally and displays the Veeam Host Management screen, but I can't access the network configuration because the keyboard input doesn't seem to work correctly.ENTER to change the network config!What I've tried:HTML5 Remote Console Java Integrated Remote Console (v252) Different browsers Hotkey programming Ctrl+X Ctrl+Shift+X Fn combinations Java updated to the latest versionThe problem is that Enter does not activate the "Sign in" button, so I can't get into the Host Management menu to change the appliance IP address. The appliance currently has an incorrect IP configured, so I can't access the web interface or SSH.The server is in a remote datacenter, so connecting a physical keyboard isn't an easy option.Has anyone experienced this with the Veeam Appliance or iLO 5?Is there a known workaround to get Enter

Setup:On-prem VBR 12.3.2 Veeam Backup for Microsoft Azure appliance, connected via External Repository Goal: Instant Recovery to VMware vSphere, restoring Azure VMs back to on-prem vCenter (testing DR failback scenario)What I've confirmed:Restore points ARE visible in VBR under Home → Backups → External Repository → Failback storage Each VM already shows 5 restore points. Platform shows correctly as Microsoft Azure, repository FailbackThe issue:When I right-click a restore point to start the recovery, "Instant Recovery to VMware vSphere" is not available / grayed out in the menu, even though the restore point is clearly present and shows 5 valid points.Questions:What conditions cause Instant Recovery to VMware vSphere to be unavailable even when a valid restore point is shown in the console? Does an active/running backup job on the same policy (I currently have other jobs running in parallel) block Instant Recovery for these VMs? Are there specific requirements for restore points impor

Hello,We are facing a backup issue with Veeam Agent for Microsoft Windows on one specific Windows 11 Pro workstation.We have two Windows 11 Pro PCs, both fully updated and both backing up to the same SMB share.On PC #2, backups work fine.On PC #1, backups always fail.The job starts normally and goes through: Initializing Preparing for backup Creating VSS snapshot Calculating digests Reading EFI partition Reading OS (C:) The failure occurs during Finalizing with the following errors: Application is shutting down. Unable to retrieve next block transmission command Exception of type 'Veeam.Backup.AgentProvider.AgentClosedException' was thrown What we already tried: Reinstalled the agent Recreated the backup job Updated the agent to 13.0.2.1102 Disabled antivirus for testing Confirmed SMB 3.1.1 Added this registry key:HKLM\SOFTWARE\Veeam\Veeam Endpoint BackupForceBufferedAccess (DWORD 32-bit) = 1 We also checked VSS earlier: writers are stable and the backup does not

Hello everyone!This is my first contribution to the Veeam Community Hub!In the long term, I plan to start my own blog to share my thoughts and technical perspectives from my daily work, but while it is in the making, let's move on with my thoughts on the topic „how to structure jobs.“This post will cover Veeam Backup & Replication in the first place, but in the future I will also cover Veeam Microsoft 365.In my daily work, I have seen a lot of variations, like “naming schemes“ (please imagine this in very large quotation marks), like "Backup Job 1“ or „Server Backup x with Database.“Basically naming jobs like this, of course, works, but in the daily work you have to search for what this job is exactly, and when the description is the default one, you don't know anything.To prevent this situation, and because I really like to organize things:)Over time, I have developed a specific naming scheme for jobs in Veeam Backup and Replication, such as Backup to Disk or Backup Copy Jobs.This

  I'm documenting a full move from VBR v13 on Windows to the v13.1 Software Appliance, run for real in my Pure Storage lab before any of it gets called a production map. Part 2 of the series just went up, and it's the architecture conversation, so I wanted to share the highlights here where the architecture arguments actually happen.The premise: the worst time to make design decisions is mid-migration. The appliance model changes enough old defaults that the target deserves a fresh sheet of paper, not a copy of what your Windows server had. Here's what ended up on my sheet.The backup server is now an appliance you don't log into. The VSA gives you a hardened, Veeam-managed Linux base with no OS access, and after years of preaching simplicity I find that liberating rather than scary. An OS I can't touch is an OS I can't break, and one an attacker finds much less interesting. The old placement rules still apply though: keep the control plane out of the blast radius of what it protects.Pr

 Why this guide? A while back, a customer asked me for a simple step-by-step guide for restoring the Veeam Backup & Replication configuration onto a newly deployed Veeam Software Appliance. This write-up is the result. It has been a little while since then (as you can tell from the version used, 13.0.1) - but since I haven't found a similar step-by-step guide here in the Community Hub yet, this one is for you. I am well aware that most of the steps here are self-explanatory for all of us, and that most of you could get through this configuration blindfolded. My customer, however, asked for a truly foolproof guide - something to provide a rough direction in a worst-case scenario. That said, should it ever come to that, we will of course be supporting them anyway...And finally, the customer also receives a checklist to document the individual steps - you will find it at the end of this guide.  VBR / Veeam Backup Server Configuration Restore  If the entire Veeam VBR intelligence is no

 Have you ever wondered where we Veeam 100 members are distributed around the world?Based on Veeam 100 Directory | Veeam Community Resource Hub and the public location information I have from our LinkedIn profiles, I sat down and provided a world map that answers exactly the above question, or shows it on the map. In the backend, I use MapGeo and Google Sheets for this. As soon as you press directly on a member or their point on the map, the photo stored from the Veeam 100 Directory (in the Community Hub) opens.For short information such as names, titles and, if applicable, Blog URL just “hover” over the point on the Map. Below the map is a search mask, here you can jump directly to the corresponding member, which also opens the stored profile picture (see above). If you want to continue searching, just click outside the photo. Now only ​@safiya, ​@Madi.Cristil, ​@NikolaPejkova, ​@HannesK and ​@Rick Vanover need their own category in the Veeam 100 Directory with a photo, so that I can

Recently, one of our clients experienced a situation that perfectly illustrates why operational resilience must be at the heart of every IT strategy regardless of any external threat.📖 The ScenarioWe were in the middle of building a new infrastructure, which was not yet operational, when the client suffered the loss of both server rooms within 48 hours of each other.The cause? Not ransomware. Not an intrusion. Simply the simultaneous end-of-life of SSD drives after nearly 8 years of operation.The tiered storage architecture amplified the impact: as soon as the SSDs reached their endurance limit, the first site collapsed overnight. Investigation quickly confirmed the diagnosis. But the second site, running the same architecture with the same history, followed the same path two days later.Bad timing? Absolutely. ⚙️ The Operational ResponseThe situation was all the more complex as the production infrastructure was end-of-life and out of support, we were precisely in the process of buildi

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

 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

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

Yesterday I got an error for two oracle databases which are backed up via the VEEAM RMAN plugin.Strange - there are several database instances on this system, all but the two are working fine. And these two had worked up to then, too…And… I did not change anything in the VEEAM and plugn configuraton  After some discussion and research with our Oracle admin - bingo.He had moved these two databases to another Home directory and did not change the corresponding entries in the /etc/oratab. So - as shown in the picture - the backup of the database and the recovery logs worked, but the creation of the AUTOBACKUP failed and the ORA-01012 error was given.After the entries were corrected all worked fine again.Perhaps some of you will face similar issues, too. I did not find anything for this problemin the forums with a quick search.

We have a few clients that have a single physical server and have a service or application that is already using port 443.  So when we attempt to upgrade from v12 to v13, it won’t install since 443 is being used and v13 uses it for the Veeam Web Service.  Assuming we can temporarily disable this service/app to get the upgrade to complete, is there a way once v13 is installed to get the Veeam Web Service to use a different port?

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

The ChallengeYou did everything right. You planned the maintenance window, cleared the pre-flight checks, upgraded your Veeam Backup & Replication server to v13, and expected the usual smooth ride when pushing the updated Veeam Agent to your protected workloads. Instead, the Protection Group rescan throws certificate errors, some of your agents stay on the old version, and your backup jobs on those endpoints start to look nervous.I ran into exactly this on a customer environment recently, and since the root cause was neither obvious in the logs nor documented in an easy-to-find KB, here is the short write-up. The Symptom(s)After the VBR upgrade to v13, the console tries to push the new Veeam Agent binaries to the Windows guests in a Protection Group. The deployment fails with a certificate related error, typically along the lines of:A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. Or a signature verification failure on

Hi,Recently I change my job. so that i need to change my email address, any one can help me in this issue?

Hi,did anyone or maybe Veeam itself worked on skill for Claude Code (and others)? For diferenet API endpoint, but mainly VPSC.I found (but not tried) this one https://github.com/Servosity/msp-skills/tree/main/skills/veeam  Best regards

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

Hello. I have installed the newly released version 13 of the software appliance. I also have a Synology DS923+ NAS. Both devices are separate and are not added to any domain. Could you please advise me on the safest way to connect this NAS to the newly released appliance? I tried to connect to the SMB share, but I am getting Kerberos errors. I have version 12 installed on Windows Server, and the connection works there. Now I am testing the appliance and encountering connection problems. Thank you in advance for your help.

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.

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

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