Discussion Boards

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

So it's very simple, our backup server (infrastructure appliance) had a proxy server configured for access to Internet (in order to fetch updates etc.)Everything good in 13.0.In 13.1 it seems to be trying to use internet proxy to connect to anything http(s), even “localhost”. Goes without saying that Backup server doesn't even properly start (system services can't connect to local identity service bc that sends them to internet proxy).After defining proxy exceptions for localhost etc., connections to data movers still fail, again because those connections attempt to go through internet proxy.Case is open with support. Reverted to 13.0. Careful!

We are reviewing our Veeam Backup for Microsoft Azure design to optimise Azure storage costs while maintaining best practices. Currently, our Azure VM backups are stored in GRS storage accounts, with daily backups (31-day retention), monthly backups, yearly backups in a separate GRS repository, and hourly snapshots. We also have a 125TB Veeam Data Vault subscription and use Backup Copy Jobs to maintain an immutable offsite copy of all backups. Given that we already have a secondary immutable copy in Veeam Data Vault, we are questioning whether GRS is still providing sufficient additional value to justify the extra cost compared to LRS.We are considering creating new LRS-based repositories and directing future backups there while leaving existing backups in the current GRS repositories until they age out naturally. Is this the recommended approach, and would restores continue to work from the existing GRS repositories during the transition? Also, if we retain GRS, can someone explain th

Hi everyone, During the execution of a backup in Veeam Backup & Replication version 13.0.1.29 , integrated with Prism Central  pc.2024.3.1.14 the snapshot creates a recovery point, and this recovery point has a retention period of 60 days.I cannot find where this 60-day retention period is configured. I checked the backup job, but I cannot find any information or setting related to this retention.  where this retention is configured? does anybody know?  

Hi everyone,I’m testing the Malware Detection capabilities in Veeam Backup & Replication v12.1 (or latest) and wanted to check if this behavior is expected.Here is what I did step-by-step: Enabled Inline Entropy Analysis under the main menu's Malware Detection settings. Placed .onion links and ransomware notes inside a test VM. Enabled the Malware Detection option within the Backup Job settings as well. Executed the Backup Job. The job completed successfully without throwing any warnings, alerts, or failures.However, when I ran a SureBackup job on the same VM, it successfully flagged and detected both the onion links and the ransomware notes.Is Inline Entropy Analysis intended to catch file-based artifacts like text notes during the live backup process, or is deep artifact/file scanning primarily deferred to SureBackup/YARA scans?Any insights on how these two detection layers interact would be appreciated!Veeam version: 13.1

We manage several VBR deployments through Chef using the Veeam powershell module. In testing Veeam 13, we can’t seem to add groups with the Add-VBRUserRoleAssignment command in powershell. Veeam 12 works fine and in Veeam 13 adding local and domain users works fine, just no local or domain groups. We can add the groups manually through the Veeam BnR console just not with the powershell command. We are currently testing on Version 13.0.1.2067 however the previous versions of 13 seem to have the same problem. Has anyone else experienced this issue? 

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.

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

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