Community

Happy Friday, Veeam community! I am here with another packed Veeam Vanguard Newsletter including all content published by Vanguards during the last month. It´s a looong list full of great content, so make yourself comfortable and enjoy reading! 😎 ​@AndrePulia - My Veeam 100 Summit Experience - https://pulia.com.br/my-veeam-100-summit-experience/@AndreTheGiant - Linux versions supported by Veeam Backup & Replication 13 (November 2025) -

Hello, please give me suggestions to solve this problem. I have a problem regarding backup recovery which makes me stressed. I want to replicate or restore data from one baremetal to another baremetal in the scheme below without vSphere.Baremetal A supermicro, esxi 8.0 host (master node) Baremetal B Intel, esxi 8.0 host (node ​​replication) Baremetal C Dell R760, esxi 8.0 host (node ​​replication)I ran some replication and recovery testsVM test 1restored from baremetal A to baremetal B, successful without any problemsrestored from baremetal A to baremetal C, success, no problemsVM test 2restored from baremetal A to baremetal B, successful without any problemsrestoration from baremetal A to baremetal C, there were many problems (I will attach it below)VM test 2restoration from baremetal B to baremetal C, there were many problems (I will attach it below) 

Yesterday, during the VEEAM User Group Germany someone was missing a Maintenance Mode for VEEAM. The main problem was to keep which job was enabled and which was disabled. I wrote a script some times ago which stopped all jobs and disable them but before the state is dumped into a JSON File. On leaving maintenence the JSON-File will be read and required jobs are set to enabled again and failed jobs are triggered to restart. The scripts (and more) can be found on our github repository: https://github.com/claranet/VeeamHub/ Here are these scripts:Enter-Maintenance.ps1param( [switch]$DryRun=$False)Import-Module Veeam.Backup.PowerShellFunction log($message) { $timestamp = Get-Date -Format "yyyy-MM-ss hh:mm:ss" Write-Host "$($timestamp) - $($messa

EDIT: Title is misleading.  File2 is connecting fine but File1 is not.(Inventory right now)______________________________Veeam backup server (backup1) running enterprise plus 13.0.1.180. Windows Server 2022File1 and File2 on Windows Server 2022.  All three servers are joined to the domain. ______________________________(Story)Backup1 was running 12.3.2.3617, upgraded it to 12.3.2.4165.  After the upgrade I was able to successfully run backups on both file servers fine.  Decided to take the plunge and upgrade to v13.  This is where things started to fall apart.File2 is connecting to Backup1 and taking backups fine.File1 is not.  (Where I am at now)The issue with File1 one is Failed File1: Failed to upgrade host components. Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to res

Hi Community, For those using the Google Cloud Platform (GCP) appliance integrated with Veeam to protect workloads such as VMware VMs, agent based backups, and native GCP backups, I have a question about performance tuning.My VBR server has 32 vCPUs and 64 GB RAM, and it acts as the Gateway Server for a Google Cloud Storage bucket. What is the best practice for setting the number of concurrent tasks for this configuration to achieve optimal performance without overloading the system?  

 Hi everyone,I wanted to raise a question regarding the upgrade process for Veeam Backup for AWS.From my understanding, performing major version upgrades currently requires installing the on-prem Veeam Backup & Replication  — even if only the trial version — just to run the upgrade wizard.This feels counter-intuitive and unnecessary for several reasons: Veeam Backup for AWS is a cloud-native solution, often used in environments that don’t run any on-prem VBR infrastructure. Requiring an on-prem installation introduces extra operational overhead: Deploying a Windows VM Installing and updating VBR Managing firewall rules and connectivity For customers who deliberately chose a fully cloud-based architecture, installing an on-prem VBR instance

With the High Availability feature in Veeam Software Appliance 13.0.1, Veeam provides a neat way to make the backup server highly available. In this blog post I’ll briefly show how to configure HA, which prerequisites must be met, and what alternatives exist if HA cannot be used. Intro - The Basics The feature itself reduces downtime of the backup server in the Veeam Software Appliance. In general, two nodes are required; they can synchronize even across relatively high latencies. A manual switchover is possible, and a major advantage is automatic updates for both nodes. The goal is to offer fast disaster recovery without the need to keep a dedicated standby backup server, and then finally to restore the configuration backup. 

Hello guys,I’m planning to do the upgrade to v13.Is there any recommended way of doing it, documentation that I can follow?Thank you in advance.

Hi teamPlease excuse my ignorance as I have not done this before and would like your advise.Current VEEAM implementation has AHV proxy configured to back up the environment.A new AHV clusters will be added. My initial uneducated thought assumed to re-use the existing proxy but I think that is actually not possible now. It seems the proxy configuration cannot be altered so I think it leaves me with no choice to create new one. No biggie.Also, I noticed that there is an embedded worker for the cluster configured in the proxy.In general, Would you suggest adding more workers to the new cluster? There are 3 nodesCheers

Hi,  We currently have VBR 12.3.1 Windows installed with VHR 2.0. When I ugrpade the VBR server to V13, do I immediately have to upgrade VHR too or can I do that a few days later?ThanksEdy  

I hope you can help me with the following problem. When I perform a sure backup (Backup verification mode: Backup content verification  and content scan only), I get the following message in the log: Error: Failed to call RPC function 'FcCheckFilesystemIsAccessible': The volume does not contain a recognized file system. Please make sure that all required file system drives are loaded and that the volume is still corrupted. The email notification I receive indicates that the verification was successful. My question is why I'm getting this warning and how can I resolve it? Here are some specifications of our server: Veeam Backup & Replication Build 12.3.2.4156 Backup server runs on a Hyper-v  Hyper-v: Windows Server 2025 24H2 Build 26100.7171Bare metal: Windows Server 2022 21H2 Build 20348.4405 Hopefully you can help me with this.

Hi,A newbie here with using Veeam for Oracle RMAN backups.I am trying to understand/visualize whether the RMAN retention and Veeam Immutability are independent of each other or are they related in some way.We run our backups on the Oracle DB server using shell scripts and cron and using a RMAN catalog.We have set  CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 35 days.We do RMAN delete obsolete as well.The Veeam Immutability is 7 days.Does Veeam delete the backup files if they are 7 days old or does it delete the files if RMAN fails to delete them after 35 days? Or does Veeam do nothing unless we uses the force-delete?Kinda hoping someone has a presentation of some sort to show how this works. Have read thru the documentation and can’t find any that explains this. Or maybe it is explained more clearly/visually in any Veeam documentation and I just can’t find it.Any reply will be much appreciated. Thanks in advice.

I’m unable to run any backups on Veeam Agent for Windows (6.3.1.1074, free edition). While my setup was working previously, I now get the error “Failed to create VSS snapshot” when attempting to run a backup.My destination is an SMB share on a local Debian host. Other devices on my network (In identical configurations, “Entire Computer” and encrypted backups) are able to back up to that share successfully, it’s just this one machine that’s failing.I’ve tried the usual suspects: Restarting the machine, removing/re-adding the backup job. I also tried the steps outlined in this post:Opened an Command Prompt (Run as Administrator)Ran the following commands:net stop vss net start vssYou can also restart these se

Hi,I’m trying to configure HA on my Veeam Backup Server. Has anyone seen this or ran into a similar issue? I can ping both servers from IP and FQDN. Both have DNS entries. I ran through the pre-requisites of allowing HA to be configured from the Host Management, Now, I’m at a loss ..any ideas?  

Hi Community, good day! In my article, you will find information about some conditions that may prevent upgrading from version 12.3 to version 13, such as:Unsupported OS for the VBR server; Unsupported SQL Server version; Unsupported .NET version; Old components still registered (Cloud Connect, Enterprise Manager, Console, Agent, Plug-ins); Legacy license type, and more.Here a small table that can be used as a reference to organize the upgrade process in the best possible way; keep in mind that this is just a small example based on a very simplistic scenario.  Build a table like below:ScenarioVBR 12.3 on Windows Server 2016 SQL Server 2016 VMware ESXi 7.0 U1 Windows Server 2016 ReFS repository 

I was trying to upgrade the Veeam Enterprise Manager to v12.3.2.4165, I noticed the version is showing 12.3.2.3617 on the Upgrade page.I view detailed information about Enterprise Manager and its components, the Veeam Backup Enterprise Manager Service build: 12.3.2.4165Veeam Catalog Data Service build:12.3.2.3617Web Site Information Build: 12.3.2.3617bugs?

Hi there,I’m currently in an greenfield V13.0.1 deployment, based on the Appliance.After enabling Remote Access in the Host Management Console of the VBR system - it’s mentioned, that this will be enabled after Security Officers approval and for 8 hours… We did this yesterday. This morning, 12-14 hours later, it was still enabled.  Unfortunately I didn't checked, if it’s only a visible bug or if the service / or Port 22 is really still open. I will check this tomorrow and give another feedback. If this is the case, I will open a support ticket for it.Have anyone seen the same behaviour? Thanks and best, Markus

hello Hi, can you help me please? I have a problem with a SureBackup job in Veeam version 12.3.2.4165. When creating a script, I entered an invalid character, and Veeam let it through, but I can't delete, modify, or disable the job. I've already entered several scripts via PowerShell, but it won't delete the job. Any ideas on how I can delete it?  

This is my first blog, I’m a Team Lead and Sr. Solutions Architect for the Data Protection Practice at a Veeam partner. I work in their Solutions Lab where I provide pre-sales support and product demos for several data protection products including Veeam and Data Domain. I’ve created several Veeam demos with different use cases.  Steps to Integrate Data Domain 6410 with Veeam Data Platform v13 The PowerProtect Data Domain is a purpose-built backup appliance from Dell for cyber resilience in on-premises and multicloud environments. It combines high-performance, efficient, and secure data services with the Data Domain Platform to provide fast recovery and robust protection against threats Please follow the steps below to integrate the PowerProtect Data Domain 6410 with VBR. Prepare the Data Domain 6410Ensure the DD Boost license is enabled on the Data Domain system

Recently my colleague Claudio Fortuna published a new Best practices guide for Veeam Recovery Orchestrator, here  https://bp.veeam.com/vro/ Although considered a team effort, I can say Claudio is the main driver and author so thanks for his effort. It breaks a bit with the traditional best practices as it is more a knowledge base then a complete best practices. At the same time it does include a lot of interesting things like Clean room best practices which Claudio pioneered in the first place.But next to this release, the solutions architect teams has also updated the theme of the best practices in general. This has been a major overall so hopefully you like it. It does feature a dark mode. For the light mode, we have opted for a blue contrast color to enhance accessibility. Because of this complete overall, you might have to do hard refresh on the best practices like the 

 Veeam Backup and Replication v13 is now in the wild, and for service providers running Cloud Connect this is not just another point upgrade. It is a major platform refresh that touches the core backup server, gateways, explorers, agents, and the tenant facing control plane. With v13 bringing stronger security defaults, modernized components, and several legacy features finally retired, VCSP partners should plan their upgrades early so tenant adoption is smooth from day one.I recently upgraded my Cloud Connect environment from 12.3 to v13. In this post I will walk through the upgrade flow exactly as the wizard presents it, with short practical notes at each stage. The focus is simple. What to verify, why Veeam is asking for it, and how to avoid tenant impact while moving your Cloud Connect stack cleanly onto v13. Preparing for the upgradeBefore starting the upgrade, there are a few best practice steps you should complete a

Hi Community, Those currently using the Google backup appliance for GCP environment backups, have you recently encountered this type of update behavior? Previously, updates were applied automatically with just one click and also option works Schedule updates through the updater, but now I see an update prompt like in the attached screenshot.  Has anyone performed this update recently? If yes, please share your experience and any best practices.I want to plan this properly and avoid any disruption.

I get the error “30.10.2025 09:52:47 Error    [veeam-infra.infra.local] Failed to synchronize update settings. Error: Cannot provide with host's certificates - PhysicalHost does not exist for host 'veeam-infra.infra.local'                             b4634265-9228-4a5e-9d95-2c12313e89c6”This server has already removed from veeam configuration. Powershell-command “get-vbrserver” does not return this server… How do I fix this?