Recently active topics

 Recently, a customer asked me about Microsoft’s changes to throttling and service limits. In the past, they had used the multi-app registration approach and now wanted to clean it up. They also asked for clarification on how to handle backup settings and optimizations going forward.Regarding backup throttling and the EWS → Graph API transition, I have already published two blog posts — feel free to check them out:Microsoft EWS is dead. Long live… Graph?„Dr. Backup and the Quest for the Holy Backup Performance Stream: Mastering the Latest Microsoft Throttling Changes (March 1, 2026) with Veeam Backup for Microsoft 365 v8.4 and VDC M365Now, let’s focus on cleanup first—because multi-app registration no longer provides any performance benefits (see KB4821). Removing it is possible in both on-prem and VDC environments, but the steps differ slightly.  Step 1: Identify the App Registration IDs You Want to Remove In VDC Backup Service you can find them here:Veeam Data Cloud –> Microsoft 3

Hello,We are using VSA v13 (linux) and we use powerstrore is there still a integration with Powerstrore, like on v12 windows. There was a installer but this oviously does not work.Even tried it installing on the BR console no luck there

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?

Hello , We are planning to migrate our infrastructure from an on-premises Hyper-V environment to Microsoft Azure. Our current environment consists of: Hyper-V virtual machines protected by Veeam Backup & Replication.The Veeam Backup & Replication server is currently running as a Hyper-V virtual machine. A NAS device is used as the backup repository, which will also be decommissioned as part of the migration. We would like your guidance on the following: Does Veeam offer a cloud-hosted or SaaS-based backup management solution that can replace our on-premises Veeam Backup & Replication server? If such a solution is available, can it manage and protect Azure virtual machines while providing the same or similar functionality as Veeam Backup & Replication? ​​​​​​​If a cloud-hosted Veeam solution is not available, what is the recommended architecture for customers migrating entirely to Azure? Additionally, regarding our backup repository: We plan to decommission our existing

Hi All,I’m wondering if there is a more widespread issue with Veeam Backup for Microsoft 365?A customer has recently noticed the processing speed for their M365 jobs is grinding to a halt and not finishing at all. They have tried many things including provisioning a physical server with SSD but the job processing rate remains very low.Are there any suggestions to improve this? They are on the latest version and only noticed the issue within the last few weeks.Setup - One Server, One organisation. 4 jobs to process - Mailboxes, SharePoint, OneDrive and Teams.Using one account for all jobs. Any guidance would be appreciated. Thanks, Peter.

Hi,We are just moving customers away from VMWare to HyperV and I have got a problem at one site.I have added a Ubuntu 24 server as a backup proxy onto the DRHost. I then added it in Veeam, and I can see it in the list of Backup Proxies, but I am unable to select it when trying to set it up in the available proxies in the job.It isn’t greyed out, and it went through the setup pretty much okay. I did get this message:veeam cannot find nfs mount tools on the linux machineI am not sure if I need that though, sorry, not an expert on this bit.At the moment the server is not in the box of available proxies.Can anyone help?

Olá time!Se inscreva e aproveite essa oportunidade única de participar desse evento!   Link: Proteção do Microsoft 365 e EntraID com Veeam, Thu, 9 Jul. 2026 at 19:00, America/Sao_Paulo | Veeam Community Resource Hub

Hi everyone,I noticed an interesting behavior during DataLab testing. Multiple runs of the same DataLab test are producing different restore outcomes.For example, in one run, VM A completes with an error, while in the next run the same VM completes successfully. I have also seen the opposite behavior with another VM.I would have expected the test results to be consistent and repeatable, especially since nothing has changed in the environment between the runs.Most of the VMs involved are running older versions of Oracle Linux Server.Has anyone else observed this behavior before?Kind regards,Chris

What are the prerequisites for using Changed Block Tracking (CBT) with VM backups in Veeam Kasten on OpenShift Virtualization 4.21? How can we validate that CBT is enabled and being used during backup operations?If the CSI driver does not provide native CBT support, is there any workaround that combines the CSI driver with KubeVirt, libvirt, or QEMU modifications or configuration changes to enable incremental backups based on changed blocks?

I try to use Veeam13 appliance version, and need help can/how i can mount the iscsi drive to the veeam13?

Hi everyone,I have been testing Veeam Backup with Proxmox and overall I think the integration is a good and important step. The Veeam Backup Worker concept also looks promising and works reasonably well so far.However, compared to VMware-based jobs, the current Proxmox implementation feels less flexible in a few areas. I would like to share some feedback and also check whether I may have missed something in the configuration.The main points are:No backup encryption option visible In the Proxmox backup job settings, I currently do not see an option to enable backup encryption. This is something I consider important, especially when backups are stored on shared repositories, offloaded, or handled as part of a broader security concept. Is encryption currently not supported for Proxmox backup jobs, or is it configured somewhere else? No job chaining / “start after another job” option For Proxmox backup jobs, it looks like I have to configure a fixed schedule, for example a specific daily s

Dear Experts,I'm validating Veeam Backup for a client.I would like to back up VMs on Nutanix AHV.I created a backup worker by referring to the following documents.https://helpcenter.veeam.com/docs/vbr/userguide/ahv_workers_add.html?ver=13So, I have some questions.Our customer wants to synchronize the time of this WORKER with their NTP server.Q1) Is it possible for Veeam's WORKER to synchronize their time with their NTP server?Q2) Could you please tell me how to synchronize the Veeam worker with their NTP server?I apologize for asking such a very basic question, but could you please tell me?Kind Regards,Hideki

Hey team! Wanted to flag something that might be worth checking out. 👀Our Women in Green co-leader (internal Veeam ERG group), Dangvy Keller, is speaking at the Channel Focus Women's Leadership Council virtual event on July 21 (8:00-11:15 a.m. PT).The Women's Leadership Council brings together influential women leaders in the channel industry to foster collaboration, share knowledge, and drive meaningful change. It's a community built to empower women to lead with confidence, break barriers, and pave the way for future generations of female executives.This year's virtual event is designed to “ inspire, empower, and connect women leaders from across the industry”. You'll hear from thought leaders, share insights, and explore strategies to advance your career and leadership impact. The theme is "How to Stay Real and Rise in an AI Era," with panels on evolving job roles, mentorship, and resilience in an AI-driven industry.It's free and virtual, so easy to hop in for all. Register here: C

I am a first time Veeam customer trying to set up a new test environment using a trial license in hopes to purchase it. I have one physical HPE server that is running the Veeam VSA installed from the latest ISO file.  This is the only backup repository.  I have a second physical HPE server that is running Windows Server 2022.  This has a tape drive connected to it.  This also is the windows mount server.  I also have a laptop that I’m using just for management purposes with the console installed. I have a third physical server with Hyper-V on it.  I was having no issues backing it up but I created a new virtual machine with 2 large disks for testing and pointed it at the VSA iso file and during install chose the Veeam Enterprise Manager option.  I am not totally certain but believe this is what broke backups for me.  Now when I try to backup any of the virtual machines on this Hyper-V server I get an error “Unable to detect the VBR BIOS UUID. This error likely appears because the Veeam

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

This is the second time my Veeam 13 console cannot connect and shows the error below.The first time I faced this issue, I reinstalled VBR and it worked normally. However, now that I am facing it for the second time, I feel there might be a bug in this version.After checking the Veeam services, I found that there are three services that cannot start:Veeam Backup Server RESTful API Service Veeam Explorers Recovery Service Veeam Web ServiceHas anyone else experienced the same issue?   

Con un termine tecnico che usa qualcuno, sono sempre stato una “half saw” nella programmazione, e questo è naturalmente un handicap quando viene comodo fare degli script di automazione/raccolta dati e chi più ne ha più ne metta.Negli ultimi anni ho iniziato ad approfittare delle capacità di scripting della AI. Fino a qualche mese fa usavo chat con ChatGPT o Gemini e il processo era fatto di copia incolla, richieste, copia incolla, prova, cambia, copia incolla, cheidi modifica copia incolla prova etc etc.Poi sono passato a Claude e, sempre vincendo la mia poca affezione per le CLI, in particolare usando Claude Code mi sono accorto che la differenza era fra uno studente delle medie e un universitario.Siccome mi capita di parlare con amici e colleghi informatici miei coevi, che fanno gli occhi della mucca che guarda il treno quando gli chiedo se usano il “Vibe Coding”, ho pensato di fare un piccolo video esplicativo di come un vecchio esperto e un giovane apprendista virtuale possono oggi

I setup Veeam Agent 13.0.3.1220 on a new windows 11 pro computer and have been unable to get it to complete a backup task. I restarted the VSS services with no change. It’s backing up to a synology nas file share. Here are the backup details.  Creating VSS snapshot Error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{43dab221-71ff-43cf-8389-49fcb4151cd9}]. Writer's state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f0].Error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{43dab221-71ff-43cf-8389-49fcb4151cd9}]. Writer's state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [

Hello,I need some recommendations or ideas for my backup-to-tape design.I need to back up VMs to tape with the following retention requirements:Daily retention: 365 days Monthly retention: 12 months Yearly retention: 3 yearsAssuming I have enough tape cartridges available, what would be the best way to design the media pools?My initial idea is:Create one job with a media pool for daily backups. Create 12 jobs with 12 separate media pools for monthly full backups. Create 3 jobs with 3 separate media pools for yearly full backups.However, I think this approach may make restorations more complicated. For example, if I need to restore data from April 5, would I need to mount the April monthly tape as well as all daily tapes required to reconstruct the backup chain from January 1 to April 5? Am I understanding this correctly?Therefore, I am considering a different approach:Combine the monthly and daily backups into the same backup chain. Each media pool would contain one full backup followe

There’s always a bit of excitement when a new Veeam beta drops. Since I spend much of my time in the lab evaluating new features and demoing to customers, I was eager to get my hands on Veeam Backup & Replication 13.1 Beta and see what it had to offer.Instead of just reading through the release notes, I approached this the same way I would a customer proof of concept. I started with a clean installation, built out a realistic backup environment, configured the solution, tested the new features, and looked for anything unexpected along the way.In this article, I’ll walk you through my entire lab experience—from deployment and configuration to testing the latest functionality and sharing my observations. My Lab EnvironmentFor this deployment I used:VMware vSphere running on VxRail Veeam Backup & Replication 13.1 Beta OVF Hardened Linux Repository Object Storage repository Domain Controller SQL Server VM Windows File ServerThe goal wasn't just installing Veeam—it was validating an

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

During a recent recovery scenario, I had to restore a physical Ubuntu server protected by Veeam Agent for Linux and bring it back as a virtual machine in a VMware environment.The initial plan was to use the restore point and perform an Instant Recovery or a direct recovery to the VMware environment. In theory, that would be the fastest and cleanest path.However, real environments do not always follow the ideal path.Due to some limitations in the environment, I was not able to complete the Instant Recovery as expected. My initial suspicion was related to permissions, antivirus, firewall rules, or some kind of communication restriction between the Veeam components and the target VMware environment.Since this procedure had to be performed during a weekend maintenance window, and because the customer was not available at that moment to validate or adjust some of those requirements, I had to move forward with another approach.The alternative was to export the disks from the Veeam Agent back