Community

Hi Everybody,a Customer of mine posted the following in R&D forum because we have some issues with his M365 Backup. They have a Case open since May adressing this issue but there is only litte to none progress. I thought that maybe anybody here might had a similar issue in the past and maby even a solution or workaround:We’re currently facing a critical issue involving both Veeam Backup for Microsoft 365 and Veeam Backup & Replication (VBR), and we’re hoping to hear from others who may have encountered something similar.Background: After restoring Office files (Word, Excel, PowerPoint) — whether from Veeam Backup for Microsoft 365 or via VBR from local backups — the files can no longer be opened. They appear to be corrupted, even though they were fully functional in their original state on SharePoint or in the file system. Restoring to different SharePoint sites or local paths didn’t help. One notable detail: the restored files are smaller in size than the originals.Suspected C

Hi, This is a last resort post of sort as I can’t find any information on what is the expected scenario.On Solaris, our plugins were recently upgraded and pkginfo shows below with Version - 12.3.2.4165 $: pkginfo -l VeeamPluginforOracleRMAN PKGINST: VeeamPluginforOracleRMAN NAME: Veeam Plug-in for Oracle RMAN CATEGORY: application,system ARCH: SPARC VERSION: 12.3.2.4165 BASEDIR: /opt VENDOR: Veeam Software Group GmbH PSTAMP: 501cb4f0240920251001193914 INSTDATE: Dec 04 2025 14:01 STATUS: completely installed FILES: 8 installed pathnames 2 directories 5 executables 190948 blocks used (approx) In the RMAN log, it shows comment=API Version 2.0,MMS Version 12.3.0.54 Question is should the RMAN log be showing 12.3.2.4165 as well or it doesn’t matter or did we mess up somewhere during the upgrade and it is actually a failed upgrade regardless of pkginfo information? Checking /opt/veeam/VeeamPlugin

Hi everyone,We’re running Veeam Backup & Replication 12.3.2.3617 Community Edition and during the Backup Copy job that copies to a USB drive the “Backup Copy USB.vbm” is not saving backup meta.Error message:Failed to save backup meta to [\\ServerName|usb|Backup Copy USB|Backup Copy USB.vbm] Error: Failed to call RPC function 'FcRenameFile': An unexpected network error occurred. Failed to rename file from [\\ServerName\usb\Backup Copy USB\Backup Copy USB.vbm_13_tmp] to [\\ServerName\usb\Backup Copy USB\Backup Copy USB.vbm].I went through several troubleshooting steps in Veeam Backup to try to fix the recurring error with the VBM file.Troubleshooting steps taken were firstly to disable Indexing on the USB external hard drive.I also forced Veeam to rebuild the .VBM file on the external USB hard drive.I copied existing VBM file, deleted it off USB hard drive, then resynced the Disk (Copy) to USB backup job. Veeam then automatically rebuilt the .VBM. This worked, but the same error is s

Not sure if many are aware but I found this out today with my VHRs deployed from the JeOS ISO that the WebUI on port 10443 is disabled by default so you cannot connect to it.  You need to log in via a console (if a VM) and enable it to connect.  You will see a banner at the top about disabling once you are done which is just a click.Learning something new each day with v13. 😎

Hi everyone,I was in Prague a few weeks ago and I had a question to ask, but I ended up forgetting to ask it, a question that keeps coming to my mind.The question is this: what does Veeam mean? Now I've figured it out, but I want to launch this poll and here are four options, which one is correct? Let's have some fun and vote. :-)I've asked several people who deal with Veeam and they don't know.

I was going over my feed today and stumbled upon a bunch of folks talking about how Minio is now in maintenance mode: https://charts.min.io/Minio was the first S3 and I used with Veeam way back in 2019 and also used it a lot for Kubernetes. Sad to see it go but this seems to be a trend I guess.I think the lesson for everyone is make sure that there is competition and alternatives. If there are not then expect unpleasant surprises.   

Why Redhat 8.6 is supported and Rocky Linux 8.6 no?

The newest addition published today is the Veeam Recovery Orchestrator Knowledge Guide: https://bp.veeam.com/vro  This has been authored by EMEA Senior Solutions Architect(s) and reviewed in collaboration with our Product Management teams and many internal contributors to ensure it reflects proven, real-world usage. This will better support better designs, stronger security, and smoother implementations when standard help documentation is not enough.The guides are an excellent way to add value in customer conversations and validate designs. Additional resources:Other Best Practice GuidesVeeam Backup & Replication Best Practice Guide: https://bp.veeam.com/vbr​ Veeam Backup for Microsoft 365 Best Practice Guide: https://bp.veeam.com/vb365​ Veeam Security Best Practices: https://bp.veeam.com/security/​ Veeam Cloud & Service Provider Best Practices: https://bp.veeam.com/sp​ Veeam Cookbooks (task-focused “recipe” guides and videos): https://veeamcookbook.com/​ YouTube Videos: VeeamS

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) - https://vinfrastructure.it/2025/11/linux-versions-supported-by-veeam-backup-replication-13-november-2025/Veeam Backup & Replication 13 is now also for Windows - https://vinfrastructure.it/2025/11/veeam-backup-replication-13-is-now-also-for-windows/ Veeam products lifecycle (November 2025) - https://vinfrastructure.it/2025/11/veeam-products-lifecycle-november-2025/ Deprecated and removed features in Veeam Backup & Replication 13 - https://vinfrastructure.it/2025/11/deprecated-and-removed-features-in-veeam-backup-replication-13/ Security and a

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) I have also done a file copy test for "vm test 2" but it still has problems, for some reason it refuses to run on the baremetal Dell R7

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) - $($message)"}if($DryRun) { log "DRY RUN - NOTHING WILL CHANGE" }$_FILE = "$PSScriptRoot/job_states.json"if( [System.IO.File]::Exists($_FILE) ) { log "State File already exists - remove it first!!" pause Exit 1}# Create new, empty state fileNew-Item -

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 respond.' (0:01:04)The credentials used to connect to both File1 and File2 are the sa

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 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?