Community

I installed the Veeam 12.3.2.3617 on a virtual Windows Server 2025 and this has been a very bad experience.  I started to migrate the repository data to the new server, but it has become very unusable.  Now when I look up the issues on the web with Veeam, other people seem to have similar issues when using server 2025 with the repository on a ReFS file system.  At this point, everything is in limbo, meaning that the server randomly hangs when Veeam runs.  30% of the repository has been moved, but I can’t seem to do anything with the server.  Every time we try to access Veeam repository it just hangs.Does anyone have any suggestions other than scrapping the Veeam backup installation completely?thanksMatt

We have to diable Backup Jobs for Updates and reboots. There is a risk of letting the jobs diabled after reboot! It would be great to disable the Jobs in the GUI for some time only! With API calls we have to diable MFA for this account what can bring a security risk!  

Let me explain the customer environment first.Customer has 3 Dell Poweredge servers (will name them pe1, pe2, pe3) and 1 Dell Powervault server. Customer uses pe1 and pe2 and has deployed 2 windows machines on them with hyperv on them respectively, pe1 has hyperv1 and pe2 has hyperv2. Customer has taken the storage of these hypervs from the Del Powervault server so that they have a large size. Customer has deployed a windows server on pe3 where veeam has been installed and the backup repository is on that pe3. Now, we added the 2 hyperv on veeam by adding them as standalone hyperv, hyperv 1 has 6 windows VMs under it and hyperv2 has 5 windows VMs under it.One of the windows VMs is showing a used capacity of 50 GB. Now this windows machine is a file server, has 2 partitions, the C partition where the 50 GB is used , and another Partition, the D partition that has almost 3 TB of files on them.On Veeam i only see the 50 GB used. If i run a backup schedule in order to backup the VM, this m

Dear,Have a good day!!I would like to report an issue with Veeam Backup & Replication version 12.2.0.I upgraded Veeam Backup & Replication from version 12.1.1 to 12.2.0. After the upgrade, I attempted to update the server components in Veeam, but the process failed, as shown in the attached picture.Could you please assist me in resolving this issue? Thank you! 

Many companies breathe a sigh of relief once they have implemented a professional backup solution like Veeam Backup for Microsoft 365 for their Microsoft 365 environment. The assumption is: „Now our data is safe, and the backup topic is taken care of.“ However, it’s not that simple. Unlike traditional SaaS services, where the provider often bears full responsibility for the service, with Veeam Backup for Microsoft 365, a crucial part of the responsibility remains with the customer.’’ This means: Even though Veeam reliably handles the backup and recovery of your M365 data, you as the customer are responsible for the availability and integrity of the backup service itself. This includes maintaining and managing the underlying infrastructure (such as the backup VM), ensuring accessibility of the backup software, and guaranteeing the permanent availability of the backup files.But it’s not just the actual backup data that deserves attention. A frequently overlooked but essential aspect is t

This article explains how to set up Veeam Backup Enterprise Manager (VBEM) and manage user roles. VBEM provides a centralized web-based management and reporting platform that allows administrators to control multiple Veeam Backup & Replication servers from a single console.This article covers deployment steps, accessing the Enterprise Manager interface, and configuring user accounts with specific roles. The guide also highlights best practices for assigning permissions and securing access, ensuring efficient management of Veeam environments.Since my goal is to create articles detailing every product and feature, today I bring you a walkthrough on how to set up Veeam Enterprise Manager and manage user roles. How does VBEM fit into the broader Veeam ecosystem?In architectural terms, VBEM is a centralised management and reporting layer as discussed above. It is positioned above multiple Veeam Backup & Replication instances, as shown in the image below.Data aggregation layer: Enter

Hello, I try to restore some email for specific user let say user1@mydomain.com but i have error :When restore using user1@mydomain.comNone of the required roles (Global Administrator, Exchange Administrator) is assigned to the user : user1@mydomain.com When restore using administrator accountFailed to open mailbox : user1@mydomain.com. Failed to Access mailbox. The specific object was not found in the store. Default folder root not found. Anyone know why?

[Post updated on January 23rd]As a Solution Engineer, I never demo or validate a solution in production, and I shouldn’t. MS Dev tenants are the standard: isolated, safe, and disposable.On paper, they’re ideal: all M365 services are provisioned, licensed, and ready.In reality, they’re empty shells. Blank mailboxes. Empty SharePoint sites. Silent Teams. No data, no history, no behavior. And without behavior, I can’t properly demonstrate, test, or stress a solution.That’s the real issue: I don’t need just a tenant, I need a living environment. One that reflects real-world structures, volumes, permissions, and inconsistencies. Without that, demos feel artificial, performance tests are misleading, and edge cases only appear in production.I started by building scripts to automate content creation in M365. It worked, up to a point.As soon as I needed randomness in the assets, multiple item types, and all their specific behaviors, the setup became increasingly hard to manage. Too many scripts

Many vendors talk about "ransomware resilience".In real production environments, what are you actually doing with Veeam?Immutable repositories? Air-gapped? Object Lock?What failed in real attacks?Looking forward to your experiences and honest feedback.This could be valuable for everyone designing resilient backup environments.

A new blueprint has been added to the Veeam Communities hub site in collaboration with Joe Gremillion. The E-Series is a general-purpose all-block SAN array. This design includes copying jobs to Veeam Vault. We currently pair an E-Series model with a Veeam hardened repo for immutability support. The E-series family includes the E4012 and the E4060 The E4012 has a 12-drive disk shelf with external storage capabilities of up to 96 drives hybrid HDD or SSD. The E4060 has a 60-drive disk shelf with external storage capabilities of up to 300 HDDs or 120 SSDs. Customers have been buying this SAN array for backup targets, HPC, Video Surveillance and a JBOD. The link to the NetApp E-Series tech specs are below.Veeam NetApp E-Series Security BlueprintNetApp E-Series Technical Specifications

Hi AllI’m currently assisting a client with a Veeam ONE deployment and they would like to send alarm notifications directly to Telegram in addition to the standard email alerts.Has anyone successfully implemented this type of integration? What method did you use? Was it done specifically with Veeam ONE or through Veeam Backup & Replication events? Has anyone tested or confirmed that it still works with Veeam 13? From what I have found it is possible, by default Veeam ONE natively supports email and SNMP notifications, with other integrations typically handled through scripts or external tools.I’m trying to confirm real-world experiences and any recommended approaches before implementing it for the client.Any guidance, scripts, or best-practice recommendations would be appreciated.

The error that I am getting is Outdated being agents, please upgrade or remove the following theme Agents from the production configuration. Shared-FS01 Veeam agent for windows 3.0.1.1039. And we got rid of that file share. But for some reason Veeam is still seeing it as a stale agent. I went back to the beam backup and replication console went to infrastructure physical. I found it an unmanaged, but it wouldn't allow me to delete it. So I tried creating a temp protection group. And the era I got was remote deployment and management is available for license agents only. Please change your backup service settings to allow manage agents to consume the license then perform a protection. Rescan. Then I went back to unmanaged and it disappeared.Sorry, I know to this whole Veeam thing. I have been tasked with it and I have very little experience with Veeam. Thanks.

Last Fall Veeam released Veeam Data Platform (VDP) version 13. I have yet to upgrade myself, but have reviewed their What's New document and skimmed through the User Guide a bit. After doing so, I thought I would share with the Community some hidden features in this newest release I think you should be aware of. I have done similar posts for previous Veeam VDP versions, but this will no doubt have more content because 1. this is such a drastically new & feature-rich release, and 2. there is just so much more I think I should mention!I think we are all aware the new VDP v13 release now comes not only as an optional Linux Veeam Software Appliance based on Rocky Linux (Community Edition not supported) and has High Availability capability (Premium Edition only), but there's also a nifty WebUI available you can use to manage your backup environment. Though keep in mind, as was with the VMware vCenter Software Appliance when it was first released, there are quite a few missing features i

Hello, Is there some Visio / Draw IO sample about common Veeam architecture ? I’m not “good” to create them and I guess there are some provided by veeam :)  Thanks for your help

Hi all,I would like to share with you that it is possible to reset the IPMI password using a bootable USB drive and physical access. This works perfectly on an OOTBI. I haven't tested it on an Exagrid, but I believe it should work as well.In the event of a lost IPMI password or a bad copy/paste during installation (note that the password must not exceed 20 characters), it is possible to reset it to its default value.IPMI password can be reset to default by restoring the factory settings IPMI module using the tools available IPMICFG, IPMITOOL. Be careful it may happen that the network configuration is restored to the factory settings, so before performing this operation, note the current network configuration. IPMICFG is available for DOS, Linux and Windows.PREPARATION:Preparing a USB key with your favorite OS (eg. Use tool Rufus to create the livecd)Download the latest version IPMICFG:https://www.supermicro.com/wftp/utility/IPMICFG/Unpack and copy the DOS directory on the stickRESTART

I was running the Community Edition ver. 8.2.0.2202 on my Windows Server 2025 when a notice appeared to install the latest update for Veeam Backup for Microsoft 365 8.3.    (Community Edition)I did that upgrade but it jacked up my system. I got an "Installation Failure" with no useful information in the log. After much searching, I found this https://forums.veeam.com/veeam-backup-for-microsoft-365-f47/unable-to-install-vbo365-on-a-fresh-windows-11-system-t101611.htmlI used some of the suggestions there and I finally got 8.3.0.2201 installed.But now I get the "No connection could be made b/c the target machine refused it." I briefly saw something about a installation issue with multi-homed servers, but I cannot find that page again. 

Happy Wednesday, Community!Some good news came from the Veeam KB Support team yesterday. There will now be the ability to change log location for all of the Veeam Software Appliances → VSA, VIA, VHR. I know there have been some posts on here for those early in testing out VDP v13 where space has become an issue on the VSA. This change allows VDP users to modify the log location to a more robust storage location on the the Appliances to hopefully mitigate encountered space issues.But keep in mind...if you do indeed modify the log location on your Appliances, there is a caveat as noted at the top of the KB -“Automated log collection tools built into both the Veeam Backup & Replication Web UI of the Veeam Software Appliance and the "Create support bundle" function within the Host Management Console collect logs only from the default log location, /var/log/VeeamBackup/ . As such, Diagnostic logging stored in a different folder, as documented in this KB, will not be collected automatica

Dear Veeam team,I am trying to uninstall VBR 13 but get stuck the issue below. I have checked both services: Veeam Backup Update Service and Veeam Backup Service. There is no Veeam Backup Service anymore.Please advise me for this case 

Last Friday was officially rolled out Veeam One training in Veeam University Pro.If you are interested in VMCE+ certification, this is the right way how to achieve it. Are still not decided? I am starting it right now and let you know about the training!  

I’m unable to connect VSPC to Cloud Connect. When I try to add the Cloud Connect server from Configuration → Catalog → Veeam Cloud Connect, it fails with “Failed to connect to the deployment service.” I’ve already tried disabling Windows Firewall and antivirus, but the issue persists. I can install the agent manually on the Cloud Connect server without any errors; however, after installation, the server only appears under Discovery in VSPC and does not show up under Catalog → Cloud Connect → Veeam Cloud Connect Integration. Both servers are on the same subnet with no firewall in between.  

Backup for vmsrv0 on hyper v host1 worked always before, but for hyper v host1 i forgot that i turned off vmsrv0 vm LOL, so veeam was backing up a turned off vm. I went into host1 and switched from vmsrv0 to vmsrv1 running the same/replica (OS-Suse Linux Enterprise 12), did not continue backup chain, i just created a new backup to drive. Now i get vmsrv1 Processing vmsrv1 Error: Error: The requested operation could not be completed due to a file system limitation Asynchronous request operation has failed. [requestsize = 1056768] [offset = 240544063488] Failed to download disk 'drive_1_backup.vhdx'. Reconnectable protocol device was closed. Failed to upload disk 'shadowSpec>' Agent failed to process method {DataTransfer.SyncDisk}. Hard disk 2 (4 TB) Error: The requested operation could not be completed due to a file system limitation Asynchronous request operation has failed. [requestsize = 1056768] [offset = 240544063488] Failed to download disk 'drive_1_backup.vhdx'. Reconnectable

​ ProxyPool Swapper for Veeam Backup for M365If you regularly onboard new tenants in Veeam Backup for Microsoft 365, chances are this scenario sounds very familiar.A repository gets assigned to a proxy pool, and at some point you want to move it—quickly and without hassle. A common approach is to use a dedicated onboarding proxy pool for the initial full backups of new tenants, and a separate, permanently assigned pool for ongoing operations. Once those initial backups are complete, only incremental, day-to-day changes remain. These smaller, predictable workloads can then be handled by a proxy pool that’s specifically designed and sized for daily processing.From an architectural perspective, this makes perfect sense. From an operational perspective… it can get a bit tedious.Another use case I frequently run into is the need to quickly access logs for a specific job or repository. To do this, I assign the repository to a local Windows proxy, which gives me easy access to the proxy logs.