Community

Attempts to back up a Wallix Access Manager virtual machine recently deployed at a customer's site on HyperV result in the following error:Processing Acces Manager V5 Error: VHDx:CVhdxDisk.InitialValidation: Incorrect bitmap entry type (PAYLOAD_BLOCK_ZERO): See [MS-VHDX-v1.00-20160128] specification section 3.4.1.2. Agent failed to process method {VHDX.GetDiskInformation}.I edit the virtual disk to made a conversion from vhdx to vhdx from Hyper-v panel, but it doesn’t work.Do you have any ideas on how to fix this problem?Many thanks,Morgan

Hello Veeam Support Team / Community members I am experiencing an issue with Veeam Agent for Windows that prevents it from starting on my server.- Product: Veeam Agent for Windows (installed via .exe)- OS: Windows Server 2016- Hosting: Virtual Private Server (VPS) on Hetzner Cloud- Virtualization: Managed by Hetzner (type unknown to tenant)**Error message:**"Failed to restore client id. WMI method call failed. Object reference not set to an instance of an object."**Troubleshooting steps already performed:**1. Verified WMI service is running — no errors found2. Ran `winmgmt /resetrepository` and `winmgmt /salvagerepository` — issue persists3. Checked Win32_ComputerSystemProduct UUID via PowerShell — returns empty/null value4. Fully uninstalled Veeam Agent, cleaned registry and program folders, reinstalled — same errorThe Hetzner VPS environment does not expose hardware identifiers (UUID) to the guest OS. The WMI query `(Get-WmiObject -Class Win32_ComputerSystemProduct).UUID` returns no

 I  have 1 backup that is unable to scan, I’m getting the error : 5/27/2026 11:18:04 AM Failed : Scanning for viruses fuse: mountpoint is not empty fuse: if you are sure this is safe, use the 'nonempty' mount option Unable to mount device [/dev/loop26] with filesystem [ext4] to mount point [/run/media/Veeam.Mount.FS/9bb20087-b8ef-47b7-8fe3-ffd91c43c73b/vg_root_0-lv_root_0/storage/core]. Agent failed to process method {Mount.GenericMount}.  (fuse: mountpoint is not empty) (fuse: if you are sure this is safe, use the 'nonempty' mount option) (Unable to mount device [/dev/loop26] with filesystem [ext4] to mount point [/run/media/Veeam.Mount.FS/9bb20087-b8ef-47b7-8fe3-ffd91c43c73b/vg_root_0-lv_root_0/storage/core].) (Agent failed to process method {Mount.GenericMount}.) (0:00:09)” The backup in question is a vcenter backup which is a linux backup, the backup repositories already have the new linux mount server I made as the default mount server. I don’t have any other available option to u

Hello,Updating the windows console to 13.0.1.2067 is systematically failing with the error “Failed to update the backup console: Failed to deliver update specification to backup server.”I’am using a VSA - current build 13.0.1.2067Even when downloading directly the 13.0.1.2067 ISO, i get the same issueAnyone had the same problem and could fix it ?RgdsJIhad

Hi Community.  I am unable to resolve the above referenced issue.  This happened after an update to v13.  After the install, it worked for 2-3 days. I then started to configure my tape infrastructure and when I finished, I was prompted to reboot the server.  Now I can’t get back into the console.  Any help would be greatly appreciated.

VB365 Exchange Online backup is failing for 1 mailbox out of 600. Initially received EWS ErrorMailboxStoreUnavailable (“The mailbox database is temporarily unavailable. Cannot open mailbox”). After reruns, 2 affected mailboxes succeeded but 1 mailbox continues to fail with HTTP 403 Forbidden.The O365 team confirmed the user account is disabled, the Exchange license has been removed and the mailbox was converted to a shared mailbox.Has anyone seen this behavior with recently converted shared mailboxes? Can VB365 back up an unlicensed shared mailbox or are there specific mailbox attributes that should be verified? VB0365 Exchange Online backup is failing for 1 mailbox out of 600. Initially received EWS ErrorMailboxStoreUnavailable (“The mailbox database is temporarily unavailable. Cannot open mailbox”). After reruns, 2 affected mailboxes succeeded, but 1 mailbox continues to fail with “Failed to access mailbox, the request failed with  HTTP 403 Forbidden.The O365 team confirmed the user

The HPE Discovery 2026 concluded just two days ago, and important initiatives were announced that significantly strengthen the 15-year partnership between Hewlett Packard Enterprise and Veeam.As we know, many companies are moving their AI projects from the pilot phase to production.However, capabilities and requirements related to data governance, compliance, sovereignty, security, and resilience are becoming essential. It´s necessary to ensure that AI models have access to reliable information and that confidential data remains compliant with regulatory requirements.These challenges are directly related to the growing use of AI applications and autonomous agents interacting with enterprise data and business systems.For all interested in this topic, I recently explored some of the governance and security challenges associated with autonomous AI systems in a separate article: Agentic AI: Managing the Autonomous Risk - CloudnRollAt the same time, cyber threats, ransomware attacks, and da

Hello Expert, I am getting below error during windows agent backup. Basically job was in hung stat on VBR so i stopped the job and restarted the services on agent servers. we tried to recover the backup but its failed with error "Job unexpected failed" in error log i could see below error. These nodes backup was running fine since last few years. Since this node belongs to DB we cant reboot it. Any suggestion or guidance is highly appreciated.Info (3)    [RPC] RPC confirm session has been created. Id: {7a87b}Info (3)    [RPC] Destroying RPC confirm session. Id: {7a87b}Info (3)    [RPC] RPC confirm session has been created. Id: {52fb05}Info (3)    [RPC] Destroying RPC confirm session. Id: {52fb05}Info (3)    [RPC] RPC confirm session has been created. Id: {898fab}Info (3)    [RPC] RPC confirm session has been created. Id: {0fc04}Info (3)    [RPC] Destroying RPC confirm session. Id: {0fc04}

hello, i am not able to install veeam agent VeeamAgentWindows_13.0.3.1220.exe on my personal laptop running W11.25H2 and latest windows updatesplease advise and thanks muchfrom the logs[19.06.2026 09:38:18][INFO] Creating Installer Application instance.[19.06.2026 09:38:18][INFO] Enumerating OpenSSL v3.0.0 FIPS related products...[19.06.2026 09:38:18][ERROR] System.ComponentModel.Win32Exception (1605): This action is only valid for products that are currently installed.   at Veeam.Setup.MsiLibrary.VmMsiCommon.GetProductInfo(String strProductCode, String strProperty)   at Veeam.Setup.Endpoint.Core.VmRelatedProductsCollector.Collect(ProductConfiguration msi)   at Veeam.Setup.Endpoint.Core.VmRelatedProductsCollector.Collect(VmProductList`1 products)   at Veeam.Setup.Endpoint.Core.VmSuiteStateManager.Initialize()   at Veeam.Setup.Endpoint.Core.InstallerApp..ctor(StartupConfiguration startupConfiguration)   at Veeam.Setup.Endpoint.App.App_OnStartup(Object sender, StartupEventArgs e)   at Sy

 Unofficial, community-built tool — not an official Veeam product and not supported by Veeam Support. Results are estimates derived from a parsed log and should be validated against the official Veeam calculators, the Veeam Help Center, and Best Practices documentation. For final sizing decisions, loop in a Veeam SE / Solution Architect.When reviewing a Veeam environment— usually because there's a sizing conversation coming, or someone wants a second opinion on whether a setup is sane. And almost every time, the information I actually need is sitting right there in the VMC.log. Proxy count, repository layout, retention, GFS, agent jobs, whether immutability is on, what the NICs are doing. All of it.The problem is it's buried in a few thousand lines of log, and after the third or fourth time of Ctrl-F-ing my way through one of these to pull out proxy task counts and squint at retention policies, I got tired of it.So I built something to do the reading the log file for me.It's called Vee

I recently stood up a new Nutanix cluster and needed it protected with Veeam before workloads went live. If you are used to doing this with VMware or Hyper-V, the Nutanix AHV workflow in VBR v13 feels different. The proxy model is different, and the old AHV proxy appliance is no longer part of the setup.This walkthrough covers the adding the Nutanix environment, configuring AHV workers, running the first backup, and proving both full VM and file-level restores. What you should have before you start VBR v13 with the Veeam Plug-in for Nutanix AHV installed on the backup server. Veeam documentation currently lists VBR 13.0.1.1071 or later with AHV plug-in 13.9.0.212+ as the supported baseline. Nutanix AOS 6.8.1.6+ Prism Central pc.2022.6 through pc.2024.3.1.10, or pc.7.3+. Versions 7.3.1.2, 7.3.1.3, and 7.5.0.0 are explicitly excluded. Admin credentials for Prism Central or Prism Element. iSCSI Data Service IP configured in the Nutanix cluster settings. If it is not set, backup jobs can f

Hi everyone,I updated Veeam B&R to version 12.3.2.4854 following a known security issue.After the update, all jobs no longer start automatically, even though they are correctly scheduled.Even new jobs don't start automatically.If started manually, the jobs run correctly.All Veeam services are up and running correctly.Could anyone give me some advice on how to resolve this?Thanks to anyone who can help.

 Hello guys, if you don't remember which version of Veeam Backup & Replication (VBR) was used to create a configuration backup, this command can be extremely helpful. It allows you to analyze the configuration backup file and identify the VBR version information, making it easier to determine the correct Veeam release to install before attempting a configuration restore. Veeam.Backup.Configuration.Tool.exe /file:"D:\Backup\ConfigBackup.bco" /analyzefile The command analyzes the specified .bco file and displays metadata about the configuration backup, including the Veeam version that created it. This is particularly useful during disaster recovery scenarios, migrations, or when restoring an environment after a long period without documentation.

Hello everyone,I updated a VBR console to v13, but after the update, I was unable to connect to the console and received the following message:“Failed to connect to the backup server: Access to the registry key ‘HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\Plugins’ is denied”I noticed that when I launch the console using “Run as administrator,” I can access it without any issues. I checked the Registry Editor, and the permissions are correct.What’s surprising is that I haven’t encountered this error with other customers who have upgraded to v13.I don’t know how to resolve this issue. Do you have any ideas, or have you also experienced this problem?Thanks in advance  Bonjour tout le monde,J'ai passé une console VBR en v13, cependant après cette mise à jour je ne parvenais plus à me connecter à la console avec le message suivant:"Failed to connect to the backup server: Access to the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\Plugins' is

Transaction logs are not able to start on DB servers, which could be the issue. Error: Failed to use DB:UpdateDirectBackupInfoIsOutOfSync in managed mode Case already been opened with Support. 

I’m wrapping up the first phase of my Veeam for AWS journey.I actually started this lab from some ideas I shared in the post below: In this video, I go through the full workflow:• Protecting AWS workloads like EC2, RDS, DynamoDB, VPC, EFS, and FSx• Creating Replicas, Snapshost, Backups and performing restores• Testing cross-region recovery (Virginia, Ohio, and California) Link bellow:https://www.youtube.com/watch?v=j76Xt0R55Pg&t=63s(It’s only in Portuguese, but the YouTube subtitles work really well.) The architecture looks something like this:Not exactly — I made a few changes along the way. I’ve organized the entire video into timeline chapters, like this:You can jump to any section you want. I hope this material can help someone who needs it.Thanks to ​@Madi.Cristil , ​@NikolaPejkova , ​@safiya , ​@Rick Vanover  for all the support you’ve given us.Thanks ​@NikolaPejkova for the licenses! Next up is Redshift! 

 Details: Files visible: Central_AD.vbm → metadata/config fileCentral_AD2026-06-01...vbk → Full backup (~73 GB ✅ normal)Central_AD2026-06-02...vib → ~2.4 GBCentral_AD2026-06-03...vib → ~2.6 GBCentral_AD2026-06-04...vib → ~2.1 GBCentral_AD2026-06-05...vib → ~2.5 GBCentral_AD2026-06-06...vib → ~2.5 GBCentral_AD2026-06-07...vib → ~1.5 GB👉 These .vib files are incremental backups (daily changes only)Hello Veeam Community,I am using Veeam Agent for Microsoft Windows free for office use, with no big data exchange, and noticed that the incremental backup (.vib) files for a single machine are relatively large (around 1.5 GB to 5.6 GB per day), while the full backup is about 73 GB. Machine details: - Role: Active Directory server (Central_AD) - Backup type: Incremental (daily) I would like to understand:1. Is this incremental size normal for this type of workload?2. What factors could cause such daily change rates?3. Are there recommended optimizations to reduce incremental backup size?4. How

Hi,We have a client which has Veeam Windows Agent free edition version 13 installed. The agent back up to a local USB disk. Now the client would like to have a second job to back up to our Veeam Cloud Connect console.However we still have VSPC version 8.1.0.21999 installed and our Cloud Connect Server is at level 12.3.3I know ideally we should upgrade our infrastructure to version 13 and also the VSPC console. Question is: Is it possible to add the client with the new Windows agent to our VSPC without needing to downgrade the Window agent? Ideally I’d like to install the management agent to the client laptop and use the already installed Windows agent which converts to a license version and install the second job to back up to the data center.I don’t like the idea to upgrade the infrastructure in a rush for that client.Thanks,

They want a detailed description but truncate it at about 2.000 characters :("Provide a detailed issue description and error messages." field does not accept more than that.Usually I prepare my issues in text editor and in the end copy/paste into support portal.Now I realize only half of it made it through while I don't have my original any more.I'd expect the GUI at least to give a warning. Noone serious will type his message into some web form initially and realize the input no longer works as he’s typing live.Who can fix that? Open a case for it? ;)

Hello. I am a single user, and I have a Windows 11 Home mid-range gaming PC with a 1 terabyte internal SSD for personal use. I presently have Veeam Agent for Windows (free edition, can do only one job at a time). It was 176 megabytes. It backs up my filesystem to an external 1 terabyte mechanical hard disk. There are no virtual machines here. I figured out how to use Agent without problems. It works like a charm. Set and forget. I want to add a second job, being a whole-volume-to-external hard disk job. But the free version of Agent can’t do two jobs for free. In fact, I wouldn’t mind a third job, which is to backup my most sensitive files more often. I would buy a license for Agent, but they’re only available in the UK in packs of 5! I downloaded Backup & Replication Community Edition, which is 17.9 gigabytes. It is said to allow up to 10 jobs at once. It is obviously much more powerful and gargantuan than Agent. I can’t figure out how to use it. I don’t have a separate server. I

How do I create a recovery USB drive using Veeam Backup & Replication Console 13?The methods described online and by the “Veeam Intelligence” agent don’t work for me.  

Hi all,I’m getting the above error trying to install components on my managed physical server for Veeam 12.3 . I proceeded to manually mount the iso on that server and install the components myself, but still getting the error. I’ve checked and the Remote Procedure Call (RPC) windows service is running fine.Installed the Veeam VSS Hardware Snapshot provider and checked the Registry - all present.Checked logs for the transport service at ‘C:\ProgramData\Veeam\Backup\Svc.VeeamTransport.log’ on the managed server, and seems to connect fine with agent. Did a configuration backup and performed a clean install of the backup server as some other posts suggested but still getting the error.Not sure if a clean install should be done on the managed server as well.. but not sure what else to try either. Any suggestions will be greatly appreciated. Thanks.   

 Hello everyone,I am using Veeam Agent for Microsoft Windows Free and am currently facing issues restoring a full computer backup. At this point, I have run out of ideas and hope that someone in the community can help.EnvironmentI have a PC that was protected with Veeam Agent for Microsoft Windows Free. The backup job was configured to perform a full computer backup and store it on an external HDD.Recently, the PC's Intel Optane SSD failed and had to be replaced. After installing a new SSD, I attempted to restore the system from the existing Veeam backup.ProblemWhen I start the recovery process and open Volume Level Restore, Veeam does not automatically detect the backup. However, I am able to manually browse to and select the backup files (see attached screenshot). After selecting the backup, nothing happens. When I click "Next", I receive the following error message:InvestigationAfter spending quite some time troubleshooting and reviewing the logs, I inspected the .vbm file manually.

Hello everyone, I am trying to connect the Veeam software appliance and my NAS via iSCSI. It won't work directly, so I installed Veeam Infrastructure Server, where I tried to connect the NAS, but I have no idea how to connect it there. I looked through the documentation, but couldn't find anything. Could you please advise me?Thank you in advance.