Community

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

Hi!I would like to share with y’all my initial “hands on” the VBR13 - Linux Based OVAPublishing the entry here, so you dont have to leave the Community Site:-----------------------------------------------------------------------------------------------------------------------I want to share my initial screenshots of the Linux-based Veeam Backup & Replication Server.Tech Preview: VBR on Linux (v13)Private technology preview for Veeam 100, for non-production use only. Let’s get started:As you may know, let’s deploy the OVA in our Vsphere Host:As always, follow the wizard…Select where the VM is going to be stored

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

hi,i try to install veeam  agent (i try with multiple version) on windows server 2025 but when i get to the point of installation it fails.on the log i see “ another installation is in progress” but i don’t have nothing in pending.

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!

First of all, a very happy New Year to everyone of the best community there is 😉It truly feels great to be writing here again.For those who already know me: I’ve been part of the Veeam Community Hub since the very beginning and had the honor of being a Veeam Legend for four consecutive years. The community has always been an important part of my professional journey, so stepping away wasn’t an easy decision.Some of you may have noticed that I was completely absent last year—and that I didn’t attend the  latest Veeam 100 Summit in Prague. Unfortunately, throughout 2025 my time was extremely limited, and I simply couldn’t engage in the way this community deserves. I made the conscious decision to take a sabbatical year from community activities. It was a hard call, but ultimately the right one.The good news?After a year, there’s once again room to focus on what I love:✔ sharing quality-dr

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

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.

ChallengeAfter upgrading a customer environment from Veeam Backup & Replication v12 to v13.0.1.1071, everything initially worked as expected. Existing SAP HANA plug‑ins on several systems (still in v12) continued to run without issues.Problems started when we upgraded the managed HANA plug‑ins to v13 using the Protection Group. Although the upgrade completed and the plug‑in showed v13 in the GUI, backups began to fail immediately.Error MessageError: The issuer certificate does not have a Basic Constraints extension.(Parameter 'issuerCertificate')The error appeared:During the Protection Group rescan (post‑upgrade)   During every backup attemptRoot CauseWith v13, the SAP HANA plug‑in and assumedly

Veeam continues to innovate, develop and release enhancements for Veeam plug-in Backup for Nutanix v9. Our customers keep asking for improvements and Veeam is delivering them. One major improvement was to eliminate the proxy appliance. This new version uses a worker architecture like some of our other cloud products. The worker VM is configured during the addition of the Nutanix plugin. This dramatically improves manageability and simplifies job management.  Everything is now configured in the Veeam Data Platform console. We also added the additional features below. For other improvements see the “What's New in VDP 13”. Key Architectural ImprovementWorker Archite

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

Hi all,Just a quick blog post to summarise the findings from a question that was recently posed to me.Background on VB365 Retention Modes:When using Veeam Backup for Microsoft 365, there are two retention modes possible. These are called ‘snapshot-based’ retention and ‘item-level’ retention. I won’t repeat Veeam’s documentation and you can have a full deep dive into the topic here if you’d like, but to provide a brief summary:Item-level retention leverages the creation date and last modified date to determine if an item is older than the retention period. If it is not, then it will backup the item. Snapshot-based retention protects everything that currently exists within the container (mailbox/OneDrive/SharePoint/Teams) regardless of creation date or last modified date. Once the item no longer exis

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

Hello Guys, These days Im started to experience a lot of problems with Veeam, every now and then the Veeam Backup and Replication Application and the whole server gets stuck and i could not do anything until i restart it, even some backup jobs started to fail. When i restart it goes fine for a while and then it does it again, and for the jobs a sometimes i see that the service Veeam installer service is stuck so i have to delete it and try the job again and sometimes it works.Did anyone experience this kind of issues lately? I’m having hard time dealing with this and i will be happy with any kind of support.Note:  i started to experience this issue after upgrading to 13 Version.Thank you.

I am new with veeam and i build up a software appliance V13 on proxmox VE 9.1.4The appliance is running well and i can also use the veeam console from another PC to connect.The console i installed from the community iso last version.But now i have the problem with License of community version.Where can i find the license File for the community version of veeam?Downöoad or use of online licensing?Must i send a mail to become from veeam  the license file for community version.Without the license file for community version i can not test and learn more about veeam.Do you have a link for me to solve the problem?I hope you have a answer for a new beginner on veeam.

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.

The other night, I had a weird dream. It wasn't one of those confusing dreams, but a clear vision of what our lives as backup administrators would be like in a few months. In the dream, Veeam's recent acquisitions — Securiti AI, Coveware and Object First — were no longer just logos on a slide, but a single living organism. The previews at the Veeam 100 Summit in Prague last November got me fired up to work even more. In the midst of all this confusion, I tried to bring some order, and this is what I 'saw' in my dream.(generated with Nano Banana)The evolution of the species: beyond simple recoveryRecently, us backup administrators have been talked a lot about recovery. "How secure are my backups?" How quickly can I get back online?" So, over the next few months, we'll be asking ourselves: "What am I recovering and

Dear community, Let me take this opportunity to wish you a happy new year and all the best for 2026. 🎉 I hope that your year has got off to a great start, and I have a fantastic selection of Veeamazing content for you from the Veeam Vanguards. Scroll down to see the content that our Veeam experts published in December. 🤓 ​@AndrePulia  - What would prevent migrating from Veeam v12.3 to Veeam v13 - https://pulia.com.br/what-would-prevent-migrating-from-veeam-v12-3-to-veeam-v13/ Block Repository – DAS Using Internal Disks – Part II -