Community

 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 only for upgrade purposes breaks the expected simplicity of a SaaS-like product. The appliance already updates minor versions internally — so having major upgrades depend on VBR seems inconsistent. Is there a technical limitat

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. Best regards,  Jordy

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 services in services.msc:Volume Shadow Copy Microsoft Software Shadow Copy Provider Without success. The log from my backup attempt is:6/4/2025 09:14:13 :: Initializing 6/4/2025 09:14:20 :: Preparing for backup 6/4/2025 09:14:26 :: Backup file will be encrypted 6/4/2025 09:15:07 :: Fai

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 Check the full article on my Blog https://pulia.com.br/what-would-prevent-migrating-from-veeam-v12-3-to-veeam-v13/

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  Configure storage units (MTrees) on the Data Domain for Veeam backups Confirm network connectivity (Ethernet or Fibre Chann

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 https://bp.veeam.com/vbr/ . If you don’t do a hard refresh, you might encounter issues with the menu not opening c

 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 across your VBR and Cloud Connect infrastructure. These include: 

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? 

Hi Community, We have a Synology NAS storage in our environment and would like to confirm the following: Is there any possible way to add Synology NAS storage to Veeam Backup? After adding Synology NAS storage to Veeam, is there an option to send data from Synology storage to Google Cloud Storage (Object Storage) through Veeam? Please advise if this approach is supported and share any best practices or documentation that can help us implement this. Thank you for your assistance.

Model: NUC12WSHi5Processor type: 12th Gen Intel(R) Core(TM) i5-1240PMemory: G.Skill RipJaws DDR4 SO-DIMM Series 64GBStorage: SAMSUNG 980 SSD 1TB PCle 3.0x4, NVMe M.2 2280Network: Intel Ethernet Controller I225 SeriesVMware vSphere Edition: ESXi-8.0b-21203435-standard (VMware, Inc.)Veeam Backup and Replication Edition: 12.0.0.1420PreparationDownload VMware-VMvisor-Installer-8.0b-21203435.x86_64.isoDownload VMware-VCSA-all-8.0.0-21457384.isoDownload Veeam Backup and Replication v12 isoVMware vSphere 8 Enterprise Plus licenseVMware vCenter 8 Standard Edition licenseVeeam Data Platform Advanced licenseRemark: When you try to install ESXi 7.0 or 8.0 on a system with 12th Gen Intel 1240 CPU, the installation fails with the following PSOD. You need to follow the following steps to install the ESXi 8.0.Fatal CPU mismatch on feature "Hyperthreads per core"Fatal CPU mismatch on feature "Cores per package"Fatal CPU mismatch on feature "Cores per die"InstallationCreate a bootable USB drive with ES

Protecting modern workloads requires efficiency, security, and rapid recovery. HPE StoreOnce plays an important role in the Veeam ecosystem as a purpose-built backup appliance that delivers high performance, global deduplication, and immutability for enterprise environments. While HPE Storage Servers have long been popular with Veeam architects, StoreOnce remains a strong option for customers who want a scalable appliance with aggressive data reduction for a Veeam repository. This blog takes a practical look at how StoreOnce fits into a Veeam-powered data protection strategy. We’ll explore how it supports the 3-2-1-1-0 best-practice model, how Catalyst integration and source-side deduplication reduce infrastructure load, and how Catalyst Copy and Cloud Bank Storage extend protection off-site and into the cloud. We’ll also examine immutability and dual authorization, highlight the performance gains introduced in Gen4+ systems, and look ahead to what’s coming with Gen5. For Veeam users,

I have been working on a case with Veeam Support to do with HA Clustering and not being able to enable it due to this warning -HA Cluster warning about local repositoryIt turns out somehow I tried to enable HA and then in one of my SOBRs added a capacity tier which was the cause of this.  The recommended solution -Remove the Capacity Tier (Wasabi in my case) from any SOBRs - I only had one in this case with a Capacity/Archive Tier. Enable HA Clustering which now works Add the Capacity Tier back to the SOBRs as neededWhile not the most ideal solution it works.  I asked them to check KBs or Help pages to see if this is mentioned and if not get this added as a note or something so users are aware.  Lots of testing so it was good to find this one and get a solution.

Last month I was blessed to have been able to attend my 6th Veeam100 Summit. Since I started 1st attending in 2018 (2020 was a no-go, and 2021 was a hybrid event), the venue has been held in Prague, CZ, with the exception of last year where it was held in Berlin. Though I enjoyed Berlin last year since I'd never been, I was really looking forward to getting back to Prague. It's such a beautiful city and there is certainly no shortage of places to see & go. But of course, the main excitement for me was to be able to meet up with fellow Veeam100 Community members and be given the opportunity to chat with various Veeam Product Managers.Like most years I've attended the Summit, I arrived in PRG on Sunday. Sadly, the weather wasn't too great (rainy), but no matter. First day arrivals are typically reserved for getting my bearings straight so to speak  getting to my room, cleaning up, and meeting up with other Community attendees for a late lunch/early dinner and catch up on the past ye

So it's been a few weeks after my return from yet another excellent Veeam100 Summit in Prague. This marks my 3rd visit to Prague, and I'm not getting tired of the city at all. On the contrary, I keep discovering new things to do and visit new places. This was no different this year.First of all I must thank Rick Vanover, Madalina Cristil, Nikola Pejková, Safiya Mohamed, and everyone at Veeam for creating such a unique event. Nowhere else in the Industry do you have such access to Product Management and can ask questions and provide feedback. I have seen Veeam grow from somewhat of an underdog over 10 years ago to the market leader it is today, and this is still true today.This summit was definitely focused on the release of version 13 (I think the biggest release yet, the amount of features is mindboggling) and Veeam's acquisition of Securiti AI. There is not much I can share on this, as it was made public very recent, and the purchase is ongoing.As usual, I flew out of Washington/Dull