Unanswered questions

I'm doing a full VM restore in Veeam to an HPE VM Essentials host, and I want to understand how the disk provisioning gets decided. Is there a way to force the restored disks to come back as thin-provisioned, or does Veeam just inherit whatever the target VME datastore or storage policy dictates?Trying to work out whether I have any control over this at restore time or if it's entirely determined by the destination.

Hi,I created a full system backup with veeam agent for windows on a dell laptop with Win 11 installed. I boot from Veeam recovery media to a new laptop, select the backup from external usb drive, select bare metal recovery and whatever i do (Entire, volume, manual) i receive the same error message: Restore failed: The stub received bad data

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.

1. Our environment:Veeam Backup & Replication (Advanced edition), HPE MSL3040 tape library, LTO-9 SAS HH drives, Windows Server 2025. Source data lives on a NAS file share (accessed via SMB/NFS). Processed data gets written to tape via a File to Tape job.2. Our requirement — tape verification:We need our verification to cover two layers:Read-after-write — checking tape parity and block integrity as blocks are written by the tape drive head, to ensure physical tape sectors have no write errors.Content integrity — after writing, reading back the raw file structures from tape, generating a cryptographic MD5 checksum of that data, and matching it against the original source file's MD5 to confirm the two are identical.Ideally this would be something we can run as part of an automated job rather than a manual step.3. Why this matters:Once a file is archived to tape, the source copy gets deleted from the NAS share to reclaim space. That means tape becomes the only copy — there's no going

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 ?

I'm running the latest version of Windows 25H2 version, and Veeam version 13.0.3.1220.  I installed Veeam Agent for Microsoft Windows Free version, and created the USB Recovery Media. I then did a test Bare Metal Restore.  I immediately get the error: Authentication failed, see inner exception.If I use old Recovery media created on an different PC, that is running an older Windows version with an older version of Veeam, the restore process works just fine. I don’t get the Authentication error. I found a post on Reddit, where everyone was having this same problem. One poster said he opened a support ticket with Veeam, and they acknowledged the problem. But I can’t find any information on what Veeam is doing about this very significant bug. Does anyone have an update on this bug? Is Veeam planning a fix, and where can I find a timeline? I’m not updating my Veeam version on the older PC, as I don’t want to introduce the bug on that PC. Thank you.

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

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

Hi, We are protecting a virtual machine in OCP, backup failed on export phase showing the below:status:  endTime: "2026-07-28T11:38:02Z"  error:    cause: '{"cause":{"cause":{"message":"Failure in exporting restorepoint"},"fields":[{"name":"FailedSubPhases","value":[{"Err":{"cause":{"cause":{"cause":{"cause":{"cause":{"cause":{"cause":{"cause":{"cause":{"cause":{"message":"rpc      error: code = DeadlineExceeded desc = context deadline exceeded"},"fields":[{"name":"snapshotID","value":"k10-csi-snap-d9lxt6q44c8s2sqw"},{"name":"sourceDeviceFile","value":"/mnt/sourceDevice/kanister-pvc-pnwzb"},{"name":"volumeID","value":"test112-vm-186544-mm2tf"}],"file":"kasten.io/api/datamover/client/backup_service.go:71","function":"kasten.io/api/datamover/client.(*backupServiceImpl).Upload","linenumber":71,"message":"failed      to receive upload response"},"fields":[{"name":"pod","value":"block-mode-upload-t8rqz"},{"name":"snapshotID","value":"k10-csi-snap-d9lxt6q44c8s2sqw"},{"name":"sourceDeviceFile

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

Jeżeli myślicie o migracji do VSA to ważna informacja. Nie róbcie upgradu do 13.1! Migracja na razie jest wspierana i przetestowana na 13.0.x Więcej info tutaj: https://go.veeam.com/vsa-conversion

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?

Zdravíme přátele Veeamu 💚,na konec roku opět plánujeme naše tradiční fyzické setkání VUG CZ komunity. Protože bez střechy nad hlavou to nejde, hledáme partnera/sponzora, který nám prostory poskytne.Plánujeme to podobně jako předchozí akce. 📅 Termín zhruba v listopadu, v odpoledních hodinách. 👥 Kapacitu potřebujeme pro cca 50 účastníků (klidně i víc, pokud to prostory umožní). 📍Hledáme prostory, kde se dá v klidu sedět a sledovat prezentace.Pokud máte tip na vhodné prostory, nebo byste sami rádi byli letošním hostitelem, ozvěte se. 🚀 Hostitel dostane prostor na reklamu/prezentaci firmy a zároveň možnost slotu pro vlastní přednášku na akci. Je to skvělá příležitost, jak se dostat do povědomí celé Veeam/IT komunity v Česku. Zároveň dobrý pocit podpořit komunitu. 🤝Díky moc předem za tipy a nabídky!Antonín StrnadDavid ŠevčíkPetr Bouška

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

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

I have a customer environment that was running Veeam 12 and we now upgraded to veeam 13. we have to backup the laptops and previous setting was fine but now the problem is that we cannot ping most of the laptops from the VBR13, but we can ping from the laptops the VBR13 server using ip and dns name. We have disabled the firewall on the workstations and the problems still persists, whereby we cannot ping and nslookup fails from the VBR13 server side.

 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

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.

Hello everyone, I am looking to schedule daily backup jobs and copy jobs reports using powershell in veeam backup server. Could you please provide me the suitable script for reports as per jobname, server, latest backup run time, status. Backup version is 13.0

I have been having problems with Veeam community edition failing to complete backups and giving the error “Application is shutting down. Unable to retrieve next block transmission command” at different points in long running backups.  This happened for local backups as well as remote system backups (on my network).  This error was from Veeam 12 although 11 was having consistent issues as well.  I tried new backup repo hardware, a new motherboard/USB controller, all the drive/os fixes/scans...there are no 3rd party antivirus scanners, and tried checking for volume snapshot errors.What seems to have fixed it is explicitly blocking all internet traffic (outbound) for the Veeam server executables.  What could my local backups have to do with the internet?  I have a fairly complex set of internet firewall rules with MiTM cert inspection, so I’m not surprised if Veeam gets unexpected certificate errors or failures to reach servers in background processes, but would it affect my local backup