Discussion Boards

I am running into an issue where very large incrementals are being created even when the device is having little usage. On a 1.8 TB drive (1.56 TB used), an incremental of 980 GB and another incremental of 820 GB occurred a few days later in the past week. What could be causing this? I am using veeam agent for windows 13.0.1.1009

I wanted to abandon my bare-metal Windows Server/VBR12 instance because of Microsoft and finally switch to VSA.So I set up and configured a bare-metal test installation of VSA on the server.This server has a direct connection to the HPE MSL 4048 tape library via a SAS controller.Full of anticipation, I then read: "Note that Veeam Software Appliance cannot be used as a tape server." at: https://helpcenter.veeam.com/docs/vbr/userguide/connecting_tape_devices.html?ver=13Seriously? That's incredibly counterproductive!Now I'm supposed to set up and maintain another server because VSA doesn't have the usual integrated tape server role? I also haven't found any option in the web UI to integrate and use the currently running tape library via a tape server, as is usually the case.Seriously? Did the DevOps team drop the ball here?

veeam one, new build. Was working but the user account needed a password change. I changed and rebooted the veeam one server but services wont start. All say error 1069: the service did not start due to logon failure however the account logs in fineany ideas? thanks

While trying to export.BAK file while using Veeam Explorer, it gives the following message what could be the issue. This same error appear by using instant recovery, recovering to the same location and alternate location, in addition to restore DB file to the same location and alternate location. DB Unable to attach database. | Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. | The statement has been terminated. 

[Post updated on January 23rd]As a Solution Engineer, I never demo or validate a solution in production, and I shouldn’t. MS Dev tenants are the standard: isolated, safe, and disposable.On paper, they’re ideal: all M365 services are provisioned, licensed, and ready.In reality, they’re empty shells. Blank mailboxes. Empty SharePoint sites. Silent Teams. No data, no history, no behavior. And without behavior, I can’t properly demonstrate, test, or stress a solution.That’s the real issue: I don’t need just a tenant, I need a living environment. One that reflects real-world structures, volumes, permissions, and inconsistencies. Without that, demos feel artificial, performance tests are misleading, and edge cases only appear in production.I started by building scripts to automate content creation in M365. It worked, up to a point.As soon as I needed randomness in the assets, multiple item types, and all their specific behaviors, the setup bec

B&R 12.3.1.1139 VOne 12.3.0.4670 Agent for MS 6.3.1.1074Job managed by agentA few months ago, I replaced a physical workstation that uses Windows Agent. I reinstalled the old SSD into the new computer. I renamed the PC. Everything works, including Veeam Agent backups but I noticed that email alerts and Malware scan related errors still reference the old computer name even though the new pc name is displayed in the B&R control panel.Since updating to B&R 12.3 and enabling Veeam Threat Hunter, I get the following email alerts:[Error] Malware analysis session has failed unexpectedly: Action completed with error [Failed] Daily malware detection report (0 malware events for 0 workloads)On the B&R server, I see the following in: C:\ProgramData\Veeam\Backup\Svc.VeeamDataAnalyzer.log

I understand from our network team, that the SQL agent running on Microsoft SQL 2019 causes the SQL server to lockup or the backups to lockup. Is there a method to configure the backups (data & logs) to prevent that?

Hi thereI have a question around hardened repository. A customer has purchased new hardware to implement a hardened repo and add it to the existing VEEAM setup (latest 12.x).I am trying to determine whether I should suggest to use the VEEAM Hardened ISO. I have downloaded version 2.0.0.8. Or should we stick with using Red Hat and harden that accordingly. My colleagues have done that before and we have the scripts to automate.I am new to the hardened repo game but I would think that using VEEAM iso would be simpler.What are the pro and cons?Also, maybe a silly question but it seems to me that the hardened repo is also built into the V13 virtual appliance ISO. Would it be possible to use v13 hardened repo and connect the repo to a VBR12 setup?Much appreciated.

Hello all, we are looking into SQL Server backup options, we have done a full server and a volume backup also. We see there is a Backup>Application>SQL option, however we cannot see the SQL option in our console….any ideas as we can see Oracle and Mongo available. Thanks in adavance, Tony.

Hi everyone, I’d like to get some feedback before deploying Veeam v13 in our environment. I’ve been tied up with other projects over the last six months, so I haven’t tested or worked with v13 yet. Our infrastructure is fully virtualized. We currently run two VMs: One VM running Veeam, performing daily jobs to an external Ubuntu hardened repository One physical server running Veeam, backing up everything to its own ReFS-based storage  My questions are: What is the best approach for deploying v13 — on a physical server or a virtual machine? Is it possible to use hardened storage with Veeam on the physical server?  Thanks in advance for the input!

Hi all,We have 4 physical servers debian 13 that we did backup via the veeam linux agent 6.32...before  before.We didn't upgrade our VBR to v13 we are still on version V12.3.2.4165.Is there a way we install manual on the debian server the linux agent v13 and get this servers covered without upgrading to VBR v13any ideas?Thanks,Benny

Hello all,  I’m preparing a new fresh deployment of the infrastructure for Veeam 13. First I’m installing the database with Postgres 17.7.2 and installing Veeam 13 component after (EM in this case) in a different server. I’d like to know if there is any specific requirement I need to follow as I was not able to find much about this specific case (only the recommended configuration for VBR), I guess it’s the same. I also would like to know if you recommend to separate the WAL in an specific disk separated from the DB disk as this machine is going to handle heavy workloads. Thank you in advance!Eric

how to avoid this step?  

Just a heads up combined with the questions if others noticed the same:At a customer we have an quite important Windows Failover Cluster (2 VMs) being backed up via managed agents through a protection group. For good reasons the protection group is set to “automatic agent upgrade = no”. After the upgrade of the VBR to V13.0.1.1071 we did rescan the protection group to have it notice the now outdated agents.Instead of just detecting this, the rescan immediately decided to re-install the transport service.This is quite dangerous IMHO as we specifically did not want to trigger any installation tasks without actively starting from the GUI. Did anyone else see this behavior?Thanks,Michael

I’m currently migrating from VMware to Proxmox and have run into an issue with Veeam. Backups from iSCSI only work when the VM machine version is set to 9.1.I wanted to check if you have any visibility into when full support for version 10 is planned, as reverting my VMs to 9.1 significantly reduces the usability and performance of my iSCSI LUN.

Hi VC,I’m wondering if anyone can help, I’m hopeful someone's had this before. We have two SQL servers, one which I am backing up with the Veeam SQL plugin at database level and then restoring to the other using the same plugin through the restore function.When attempting to restore I’m getting the following error:  Any ideas what I can check?Many thanks,LGH

Good day, I have a PVE 9.0.18 in my NUC, using local storage only. Yesterday I updated the VBR and Plugin to the very lastest versions. But..Well, the Proxmox plugin still isn’t working for me… it’s really strange: I configured and tested the worker successfully;I added a Windows VM (same subnet as the VBR, no firewall) to a jobIf I run the credentials test, it fails because the VM is powered off (??)The backup, even crash-consistent, also failsFor the credential test, I guess the error in the log is: “”aiting for file C:\ProgramData\Veeam\Backup\Plugins\PVE\Backup\PVE-Win_c1c3bce9-32d8-419d-b31a-6a63f6c6d2de\8fa94a5b-e558-4d50-bb67-241ff316ecab\PVE-Win.log to be unlocked”for failed backup (hot add mode)“Failed to await the Backup task 444dd208-68ee-498c-aa5a-8282d85b2369: Veeam.Communication.TypeProvider.Invoke.RpcCallException: Failed to perform backup: Failed to prepare disks for backup” 

Can we restore guest file level if the backup source is from tape? Or we must restore entire VM to the disk and then doing the FLR from disk?

Apologies if this is a frequently asked question, I’m very new to the topic of managing backup infrastructure.I’m currently facing the following issue:Server 1 is currently powered off and defective. According to users, there are important files that need to be extracted in some way. Server 1 was not centrally managed and instead had a standalone instance of Veeam Agent to run backups and copy backup files to NAS 1 NAS 1 holds a single full backup of Server 1 and is not managed via Veeam as a repository etc. NAS 1 and Server 1 are physically located at an external location with a very slow internet connection; this was the reason why the standalone agent approach was chosen in the first place Server 2 will host the restored files from the backup in the future and is managed centrallyWhat would be the best way to go about this restore process? My biggest issue is that I know how to restore files from existing centrally manage