Unanswered questions

Unprotected DB from the primary node in SQL AG. Other DBs are being backed up successfully on the same primary server.Configured to run transactional logging periodically but one large DB shows as unprotected. The problem started when the old primary node was switched over to a new server and evicted. After the eviction, it started not backing up the DB(error: Transaction logs from some databases were not backed up for the last 8 intervals).Ran image level backup (the parent job), this was successful but transaction logging still not working. However, the error now shows as (error: SQL Server transaction log backup took longer than desired log backup intervalFailed to upload SQL Server transaction log backup for DB to LogShip server: Repository agent is stoppedSQL Server transaction log backup could not be completed within 10 RPO intervals and will not be retried)This was working before and no changes to any of the Veeam servers so this error is not accurate. Confirmed application-awar

Hi, we have a Fast LTA with 5 Silent Bricks. We plan to remove them weekly, and have one brick only in the system. We want to have weekly backups rotating offsite for one month (thatswhy 5 bricks). Whats the best strategy? Currently we have one volume and one S3 share per brick, and 5 backup copy jobs, they are running on first saturday, second saturday and so on, copy of the latest backups to the brick for the current week.But what happens if there are only 4 saturdays? I have no other scheduling options to get 5 weeks. How would you implement this? Thanks.Rene

Hi, I’m having trouble implementing an immutable repository using Red Hat 10 with Veeam version 12.3.2. I installed it a few days ago and it was working fine, but today the Veeam server was shut down to fix an issue with an HBA card. Upon restarting, the machine failed to reconnect to the immutable repository, throwing errors such as: "Unexpected socket shutdown, Failed to rescan repository (...) Error Unexpected socket shutdown, host discovery failed," as well as warnings like: "Refresh linux host failed error: Unexpected socket shutdown, failed to rescan repository (...) Unexpected socket shutdown." I’ve run a number of tests: changing the user password to match what is configured in Veeam, disabling the Red Hat firewall, testing connections on ports 6160 and 6162 in both directions, and re-enabling port 22—yet nothing works. Oh, I almost forgot this warning that appears when rescanning the Linux host: "Unable to collect hardware info: Unexpected socket shutdown." It’s really frustra

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

I am in need of some assistance from the community with Veeam Backup & Replication. I upgraded the server to 13.0.1.2067. No errors were thrown during the upgrade, logs don’t show any red flags that stick out; however the service hangs when attempting to access the localhost database server.Here is what I see:When the Veeam console is run, the “Specify backup server” page appears:After the localhost database is selected, the next window appears: The console goes no further than this, and the system doesn’t show any signs of activity. All services show as running on the server:I also tried updating .NET 8 dependencies to newer versions in case these were what may be causing the issue, but there was no change in results. I have attempted to upgrade this application twice with little success. As of now, I may need to revert back to the older version and try again, which may lead me back to here.Has anyone else encountered this when upgrading to 13.0.1.2067? If so, how was it remediate

Hi,We have a 2-node Microsoft Hyper-V cluster managed by Veeam Backup & Replication Community Edition.The two nodes are:- BETELGEUSE – works normally- SAIPH – affectedThe problem is that Veeam sees SAIPH as a Hyper-V server, but its Physical Host association appears to be broken.Veeam shows:SAIPH → PhysHostId = 00000000-0000-0000-0000-000000000000and:Get-VBRPhysicalHostdoes not return SAIPH, while BETELGEUSE is returned normally.We verified that:- SAIPH is reachable- VeeamHvIntegrationSvc is installed and RUNNING- WinRM/DNS connectivity to SAIPH works- the Hyper-V host itself is operationalThe impact is that VMs hosted on SAIPH are not being backed up correctly. As a temporary workaround, we moved the VMs from SAIPH to BETELGEUSE using Failover Cluster Manager, and the existing backup jobs then work normally.An important detail: the problem appeared after the network interface cards (NICs) were replaced on SAIPH.We also checked the Veeam PostgreSQL configuration database. The hosts

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,I found this great tool a few days ago and thought we solved our problem with port postcheck after migration on v13. We will be able to control, if there aren´t left some port which aren´t  needed. Maybe it´s known problem, I tried to read some posts with restore topisc, but during those controls, It looks we found in diagrams aren´t mentioned ports for restore. Minimum what we found were, ports needed during restore of WAV agent to this agent. And for example, if I want to restore from Data Domain, I can´t see in diagram ports from mount server->Gateway server working with backup repository. Thank youRegardsRadek

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?  

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.

Hello,I am testing Veeam Agent for Microsoft Windows 13.0.3.1220 and found a behavior that I would like to clarify.I am testing a bare metal recovery scenario where the destination SSD is smaller than the original SSD, but the amount of used data is small enough to fit on the destination disk.My test environment:- Veeam Agent for Microsoft Windows: 13.0.3.1220- Windows 10- Source SSD: approximately 480 GB- Destination SSD: approximately 220 GB- Source C: partition uses less than 100 GB of actual dataI performed the following test.TEST 1 - FULL BACKUP1. I installed Windows 10 on a 480 GB SSD.2. I reduced the Windows C: partition to approximately 100 GB.3. The amount of data stored on the C: partition was less than 100 GB.4. I created a Full Backup.5. I booted the Veeam Recovery Media and selected Manual Restore.6. I mapped the backup to a 220 GB SSD.7. The Resize option was available for the C: partition.8. I was able to resize the restored C: partition and successfully restore the syst

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? 

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

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.

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

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