Discussion Boards

Hi All,I am new the the community and fairly new to Veeam and was wondering if anyone would mind sharing their own opinions and/or pitfalls  experienced using the Inline Entropy Analisis feature?My organization uses Veeam for Vsphere backup and DR and I have been asked to gather information prior to using in production.   I sounds great but from what I’ve read so far it has its limitations. Has anyone experienced any performance issues with backups or any other gotchas?   Have you found the feature useful?  Any feedback would be greatly appreciated.Thank you!

I was given a challenge, to make explain a technical process more interesting. So I came up with the gamification of an instant recovery.    Concept: "Veeam Recovery Quest"Instead of presenting recovery as a technical process, turn it into a game.  The Published Recovery Workflow (simplified)1. Incident declared2. Recovery target identified3. Backup validation4. Recovery method selected    • Instant VM Recovery    • Full VM Restore    • Application Restore    • File Restore5. Restore execution6. Validation testing7. Business sign-off8. Recovery completeBased on published Veeam recovery processes. https://victorious-beach-03fc63910.7.azurestaticapps.net/veeam-recovery-lab-clarity.html

How we can make exclusion for virus warning when backup m365 using VBO? 

Hello everyone,I am backing up MS SQL in my test environment with Application-Aware processing enabled, and I want to exclude some transaction logs. I followed the steps outlined in Veeam KB2104, but the transaction logs are still not being excluded. Is there something I might have missed or done incorrectly?Thanks.

Hi guys, Yesterday we attempted to upgrade our VBR server from V12.3.2.4465 to V13.0.2.29 but were met with the below error during the installation process -  The upgrade failed and did not allow us to retry at all. Certain options were greyed out - Checking Apps and Features, Veeam reported that it was upgraded but the app was inaccessible. -   In the end, we were forced to back out of out upgrade.Has anyone seen this before? ShaunB.

once i try to install VeeamBackup&Replication the setup refuse to complete it just once started it gives  that The error "unknown exception occurred vmaGetpropertiesFromRegistry"and close the setup and refuse to continue i am sure that happes related to uncorrect uninstalled veeam application is that mean i look for another application ?

Dear Community!Last week, I updated my Veeam environment to version 13.1. After upgading my Veeam One installation, I’m no longer able to connect through the Veeam One Client, but from the WebUI it works fine.I don’t know what is going on and I cannot contact support because I’m currently evaluating Veeam One product to see if it’s fit out needs.Here is what I have from the Veeam.Reporter.log file:03.08.26 14:10:08 [INF] 0x10f8 - 45t 2580c CertProviderService - - - - - : -->TryGetWebGrpcCert03.08.26 14:10:08 [INF] 0x10f8 - 45t 2580c CertProviderService - - - - - : <--TryGetWebGrpcCert (in 0:00:00.0013216) Thumbprint: <removed for security>03.08.26 14:10:08 [INF] 0x10f8 - 45t 2580c CertProviderService - - - - - : -->GetOrCreateCommunicationCert03.08.26 14:10:08 [INF] 0x10f8 - 45t 2580c CertProviderService - - - - - : <--GetOrCreateCommunicationCert (in 0:00:00.000948) Cert: [<removed for security>]03.08.26 14:10:08 [INF] 0x

Estou usando a Community Edition e vi que ela é compatível com o Veeam Data Cloud Vault; comprei-a em 23/07, mas até agora não consegui usá-la nem acessar o suporte ao produto. Como não tenho uma licença padrão da Veeam, não consigo falar com o suporte técnico nem abrir um chamado.

Hi everyone,I'm trying to determine whether this is a bug or if I'm missing something in my configuration.EnvironmentVeeam Backup & Replication Community Edition 13 Build: 13.0.2.29 Proxmox VE 9.2.2 2-node Proxmox cluster Shared QCOW2 storage Backup Proxy/Worker successfully deployed HotAdd transport modeProblemAll Windows VMs are backed up successfully.Any Linux/BSD VM fails with: Failed to perform backup.Failed to prepare disks for backup.So far I have reproduced the issue with:Debian 13 (fresh installation) pfSenseWindows Server VMs work without any issues.What I have already testedCreated a brand new Debian VM → same error Manual snapshot from Proxmox → works Snapshot through Proxmox API (pvesh) → works qemu-img check → no corruption Guest Processing disabled Inventory rescanned Worker redeployed VM migrated between nodes Same storage used by both Windows and Linux VMs Windows backup succeeds using the same repository and proxyExample:pvesh create /nodes/nodo2/qemu/108/snapshot

We are a vmware shop, being priced out.  Many factors pushing us toward Hyper-V.I understand that in the early days ReFS was bug-ridden in multiple aspects.Going forward with Windows 2025 CORE Hyper-V, with VM’s of Windows2022, RHEL 9, and a few linux-based OVA deployments, what is the community recommendation for the format of the iSCSI LUNs that the VM’s run from?  there will be sizes from a couple hundred GB to all the way to 6TB, and in a special case 20TB.Our Veeam Repos are XFS, so not a factor here.Thank you kindly

This is a tough situation I’ve been fighting for a week. Our windows server (2016) on which veeam Backup & Replication 12 was running on broke and we were unable to make it boot again.After much trying, I setup a new Windows Server (2025) and installed Veeam 12 on it. Before installation I installed MSSQL, imported the database from the old server and used that as an existing DB during installation. We don’t have a .bco Backup.This worked pretty well, all our backups were recognized, our configuration was still there, etc. I managed to restore the connection to our VMWare by re-entering the connection password. Now we have a Linux Backup Proxy. I reset the credentials and a connection can be established, but I am getting these errors now (from Util.VolumesHostDiscover.log): [31.07.2026 15:52:41.908]    <24>   Error (3)    Failed to unprotect data: the actual generation 1be493dd-f053-4957-86cf-06d604afcbdd does not match the expected generation ad168c2e-58e4-49d5-aa58-747ee032

Hello,We have two Veeam Backup & Replication v12 environments:Veeam Data Platform Essentials Veeam Data Platform FoundationBoth environments are isolated from the Internet, and license updates are performed manually rather than automatically.If we upgrade these environments to Veeam Backup & Replication v13, can we continue using the existing license without importing an updated license file, provided that the current license is still valid and has not expired?The following conditions apply:The current license is still within its validity period. No changes will be made to the edition (Essentials or Foundation). No changes will be made to the number of licensed instances or sockets. The environments will remain offline.Under these conditions, is a license file update required when upgrading from v12 to v13?Thank you.

Hello, I’d like to ask about an issue I’m facing.Recently, I configured Veeam Backup & Restore version 13 to back up my Windows SQL Server. The database backup completed successfully, but when I attempted to restore it on a per‑table basis, I noticed that this cannot be done via the plug‑ins. The interface looks like this:Restore interface for MSSQL Server using Plug‑InsAfter that, I checked the Veeam guide and noticed that if I want to perform a per‑table restore, I first need to configure a staging server in Veeam Explorer for MSSQL. However, when I try to add the staging server, I encounter the following error messages:Staging Server cant be added to ControllerDoes anyone know how to fix this? Any suggestions would be greatly appreciated.

Hello everyone,I'm reaching out today because we're experiencing performance issues with our Veeam backups. More specifically, I find that both the incremental backup duration and the Synthetic Full backup duration are extremely long.Here's a quick overview of our current physical infrastructure:Veeam Backup Server running as a virtual machine (connected at 10 Gbps) - 13.0.2.29 Backup Repository: Synology RS2418+ (Intel Atom C3538, 4 GB RAM, no SSD cache, connected at 10 Gbps) Disks: Disk 1: WDC WD80EFAX-68KNBN0 Disk 2: WDC WD80EFAX-68KNBN0 Disk 3: WDC WD80EFAX-68KNBN0 Disk 4: WDC WD80EFAX-68KNBN0 Disk 5: WDC WD80EFPX-68C4ZN0 (recently added, hence the different model) For every backup job, the bottleneck consistently shows "Target".Backup configurationWe currently have two backup jobs:Job 1Selected production servers Incremental backups: Monday to Friday, starting at 7:00 PM Synthetic Full: Saturday (same start time, as it's not possible to schedule a Synthetic Full earlier than t

All Veeam jobs are started failing (VMware Snapshot/Agent/Offload) suddenly with error Job cannot be started timeout 901 sec. we are on 12.3.2 version. Any suggestions or guidance is highly appreciated.Its started working fine post restart of services.

I noticed that every REST API request, including the access token request (POST /api/oauth2/token), requires the x-api-version header (for example 1.3-rev1).So I wanted to check if is there any REST API endpoint that returns the supported x-api-version (or REST API revision) without requiring the x-api-version header?

Backup job finished with Failed, Job details: Job cannot be started. Timeout 904 sec, Job has failed unexpectedlyEven the scheduled config backup job did not progress , veeam version 12.3.2All the veeam services are running fine. Kindly advise

Hello Community.I was asked by Packt Publishing if there are any influencers out there with a blog/vlog that would be interested in doing a book giveaway for a physical copy and e-book (PDF)?If you are, reach out to me via DM and I can also see for the person who does the giveaway about getting a copy of the book as well.Look forward to hearing back as I am trying to work on some traction with the book sales.Cheers - Chris

How to back up company data on a QNAP NAS? What are my options?

 We changed the IP address of a NAS used as a CIFS/SMB backup repository. The repository was originally configured using a UNC path with a hardcoded IP address and is now showing as Unavailable because the old IP is no longer reachable.Veaam ver 12.3.2Current situation:Repository type: CIFS/SMB Old repository path: \\192.168.0.8\NAS New repository path: \\192.168.0.81\NAS\Backups Repository is not listed under Get-VBRServer; it is only visible via Get-VBRBackupRepository, so KB1905 (managed server rename) does not apply. A new repository was added using the updated NAS path. When attempting to map existing backups to the new repository, Veeam requests moving the backup files from the old repository. This operation cannot proceed because the old repository path is no longer accessible. Creating a new backup chain is currently not an option due to storage constraints.Looking for the supported and safest approach to transition the existing backup chains and jobs to the new NAS repository

I’m getting the below error after upgrading Veeam servers from v12 to the latest release of v13. It’s a windows based install of Veeam, and it is connected to a (dedicated to Veeam only) AD domain.My user has local administrator permissions, Veeam Backup Administrator permissions, and MFA disabled for testing/troubleshooting purposes. The is happening across each of the Veeam v13 servers I have on the domain.It is only happening for mine and one other engineer’s user accounts, but other engineer’s accounts are not affected. We are all in the same AD groups so permissions are the same.I have tried removing Veeam Backup Administrator permissions from my account, rebooting, and re-adding, to no effect.Has anyone seen this before? Any suggestions for what else to check? In the meantime I have a case open with Veeam support, and hoping they can come up with something.Relevant logs:[19.01.2026 21:07:36.194]   <126>   Error (1)    Veeam.Backup.IdentityService.Shared.CSystemAccountProvid

7/27/2026 9:50:42 AM Failed : Failed to perform post-processing: Cannot find the backup file < XXXX_XXXXX>This is a copy job, I have rescanned the repo and as well tried initiating full backup for this VM at source, still the error exists with copy job.The copy job is immutable and can find new .vbk file created .Kindly advise.

Community,Wasabi has made a MCP (Model Context Protocol) server available to access stand-alone accounts as well as control accounts. Toolsets include: S3, IAM, and WACM (Wasabi Account Control Manager).All of the details are available here - https://wasabi.com/cloud-object-storage/mcp-for-aiNow you can utilize natural language queries to see practically anything you’d want to know about your account settings, utilization, and users. I can imagine easily integrating these tools into a support agent at your favorite MSP… 

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?