Community

 Introduction: A Journey That Started with 3-2-1-1-0Five years ago, I published my first Veeam community post about the 3-2-1-1-0 golden backup rule. That post marked the beginning of my journey as a Veeam Legend.Back then, the rule was already considered best practice. Today, it is still relevant — but no longer sufficient on its own.The threat landscape has evolved. So our backup strategies need to follow.The Foundation Still MattersThe 3-2-1-1-0 rule remains the baseline:3 copies of your data 2 different media types 1 offsite copy 1 immutable or air-gapped copy

 In a recent customer project, I was allowed to perform a new installation of the Veeam Recovery Orchestrator (VRO). The installation itself was initially completely inconspicuous – but on a German-language Windows Server operating system, which later turned out to be a decisive factor.Immediately after the installation, we authorized the local administrator group within the Onboarding-Wizard to access the VRO system. So far, so good. Or so we thought! The result: No user who was a member of the local administrators group was able to log on to the VRO system.  Error: Access denied for the user 'User-within-local-Administrators-Group': the provided credentials are invalid or the use

Hello, veeamazing community,I am back with another Veeam Vanguard Newsletter packed with tons of great content! Go and check yourself what articles published our veeamazing Vanguards during the month of March!  Across these articles and videos, the authors cover a broad set of Veeam platform operations, security, and community themes: from urgent Veeam Backup & Replication (VBR) patching and remediation of critical CVEs (including guidance to update promptly) to platform upgrade and maintenance tasks such as upgrading embedded PostgreSQL and step-by-step Veeam v13 suite upgrades (Veeam ONE, Enterprise Manager, Recovery Orchestrator, and VBR). Several posts dive into v13 architecture and hardening, including Veeam Software Appliance / VSA customization via config files (instead of Windows registry), 

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.

I’m playing with the VHR ISO and wonder how we can add a second LVM volume to the VHR.We do this for RHEL and Ubuntu builds so I’m interested if we can do this with VHR.The sort of scenario would be where you add another bunch of disks or disk shelf into a physical server (and possibly controller) so we can have a physically separate second set of storage rather than buy a new server.Some use cases:You also might want to separate remote site backups onto separate Repo’s for specific regulatory or governance requirements Getting the most value from the physical hardware

Hi, can someone tell me how to troubleshoot this? I installed Veeam on Windows 11 Home and defined its configuration, then resolved issues it reported. When I ran the backup job it reported success but no backups were created. I followed the quick start guide for a simple setup using my Dell for all components and tried backing up my C:\ drive to another drive where I would copy backup files to an ssd to keep offline.

You might have missed it but this week Mr. Cloud Connect published a blog about setting up a test KMS server! Exactly a Month ago I was thinking the same thing and found it to be a world of pain. At the time I tried PyKMIP and Cosmian but had major issues. Then I tried vibe coding a KMS DIY server with my buddy Claude (well at times buddy at others arch enemy!!). I got to the point where Veeam accepted the KMS server but then the job would fail. ​@LDelloca did what folks at his level simply do, forked the old PyKMIP and added the bits and pieces needed! He is not known as Mr. Cloud Connect for nothing, see his blog here: https://www.virtualtothecore.com/fixing-pykmip-for-veeam-integration/My home lab is not big so I try to do everything in containers and for this I looked at his forked git

Hi i have a PC that was being backed up wit veeam agent for windows free edition not managed by VBRThe PC is runing windows 10 22H2 ,After an agent update started getting the error failed to start service "VeeamEndpointBackupSvc"Tried repairing the agent , i tried removing it and reinstalling it still getting the same error .It seems something with the agent setting is wrong and removing the agent doesn't really clean all the data from the PC , tried even installing older version still the same.Also i am not seeing that service registered in services Any ideas how to purge the data ?  Or Fix this issue ?Thanks

 1. Two Backup Methods, One Recovery Console Veeam provides two distinct methods for backing up Oracle databases. The first is image-level backup with application-aware processing, where VBR takes a VM-level or agent-level backup and handles Oracle archived redo logs as a guest processing subtask. The second is the Veeam Plug-in for Oracle RMAN, which integrates directly with Oracle's native Recovery Manager and sends backup data to a Veeam repository through the RMAN SBT (System Backup to Tape) interface.Both methods feed into the same recovery tool: Veeam Explorer for Oracle. Explorer can restore databases from either backup type through a single interface. The key difference is what each method captures and what recovery options each enables.  Capability

I been trying to resote a vmware backup to a proxmox server but I can see the server and I can choose the datastore in the proxmox server but it always fails with “ Failed to prepare disk” It doesn’t matter what type of file type I choose. Has anyone been able to get passed this?

I am upgrading my Home Lab to new hardware.  Re: I can’t get the register email for mike.mckenney@scsiraidguru.comVeeam Server:  I upgraded the Veeam Server to Windows 10 22H2 from Windows 7.  I can’t install Windows 11 on this box.  I had to remove one of my three tape drives (SCSI) to go to 10.  I have two SAS tape drives.  Veeam is on 11A.   Veeam is working on all boxes except my HP Z480 below.HP Z840 Workstation:  I installed Windows 2022 Standard Server with Hyper-V.  It is in my workgroup, workgroup.  It is in the same network and subnet as my Veeam Server, Windows 11 workstaion and all VMs.  Windows Firewall is turned off.  It was on Windows 10.   Hyper-V is working.  I have 6 Minecraft Servers for our children and family to play on.   They are 8 and 10.   All Ubuntu 24.04 VMs.   Java, Bedrock and Folia.  They love to play with mods and plugins.   I can’t get to the Community Downloads for v12GA and latest v12.   I never get to

My home lab: Veeam 11 server is on Windows 10.  I have 6 Ubuntu VMs on my HP Z840 workstation with Windows 2022 Standard Hyper-V.    How do I backup each VM separate so I can recover them.   Both are in a workgroup.    Veeam won’t recognize the 2022 Standard as a Hyper-V server.   Veeam 11 can see it as a 2022 Standard Server.   Do I need to install a Hyper-V agent or Windows Server agent on this box?     

It was Christmas Eve. Most people were wrapping gifts, winding down, and logging off early. But for one of our clients  a construction company with decades of project data, intellectual property, and live customer records, that night would become one of the most terrifying in the company's history. A double-encryption ransomware attack had just taken down every system. Completely dark. Several other construction companies across the region were affected by the same attack that night. What made this attack different wasn't just its timing. The attackers were sophisticated. They didn't just encrypt the production environment they deleted the on-site Veeam Backup & Replication server, wiped the local backup copies, and went after the cloud backup repository too. I was a deliberate, calculated attempt to leave no recovery path. They almost succeeded. When the Call Came InAs a managed service provider, we know that dat

Looking for in-person Veeam VBR or Veeam ONE training in Canada. I know there are plenty of virtual options, but I’m a bit 'old school' and prefer a traditional classroom setting. Is it still possible to attend these courses in person in Canada or the US?Thanks for your tips!!

   Recently a customer asked me: “Is it actually a problem if I add a branch office with ESXi hosts that are managed by a vCenter to Veeam as standalone hosts instead of adding the vCenter? What impact does that have?” The short answer: Yes, it can have noticeable impact — functionally, operationally, and also in terms of backup consistency when VMs are moving (with vMotion). Best practice in general is to add the vCenter as the management instance in Veeam, not the individual ESXi hosts.  Okay, but why?  What is vCenter — and why is it more than “just” a GUI?  vCenter Server is the central management instance for VMware vSphere environments. It centrally manages

Lyrical IntroductionI can't believe my eyes. A product as powerful as Veeam Backup & Replication can't do simple things? Or maybe there are problems with my instance specifically? Or am I just a dumb instance?What I have.2 companies and 1 Veeam Backup & Replication 12.3.0.4165 serverWe run 70 backup jobs for these companies, without any overlapping time.1. Company 1 – 30 VMware VMs (1 job = 1 VM) – timeframe 12. Company 2 – 40 Proxmox VMs (1 job = 1 VM) – timeframe 2We also run Health Check jobs, timeframes 3 and 4, also without any overlapping time.What do I need?At a minimum, I want toreceive two emails, one containing a summary report of all backup jobs for the day, and the other containing a summary report of all health checks.MaximumI want to receive 5 emails1. 1 summary report on completed Company1 backup jobs to 2 email addresses – company1user@domain.net and admin@domain.net2. 1 s

1. This Is Not Troubleshooting Troubleshooting is what you do when a job fails and you want to fix it. Forensics is what you do when a job has been failing for three weeks and nobody noticed, a VM dropped out of protection and nobody caught it, or a ransomware event hit and you need to prove your last clean restore point. The question is not "how do I fix this job." The question is "what exactly happened, when did it start, what was affected, and can I prove it."Forensics requires a different mindset than break-fix. You are not looking for the current error. You are reconstructing a timeline. You need session history, task-level detail, bottleneck data, and alarm records across a window of days or weeks. VBR stores all of this. The trick is knowing where to look and how to correlate it. 2. Where the Logs Live VBR keeps two categories of evidence: the configuration

 When a full restore is the wrong move When SQL breaks, the first request is usually narrower than “restore the VM.” More often it is “get this database back to before the bad change” or “show me what was in last night’s backup.” That is the sort of job Veeam Explorer for Microsoft SQL Server handles well.It opens a SQL-aware view into a Veeam Backup & Replication restore point and lets you pick the recovery method that fits the problem in front of you: restore a database, recover to a specific time, roll back to just before a bad transaction, publish a database from backup, run instant recovery, or export schema and data without rebuilding an entire machine.If the backup captured SQL correctly, the workflow is familiar whether the source came from a VM backup, Veeam Agent for Windows, or the Veeam Plug-in for Microsoft SQL Server. You can launch the Explorer from the VBR console, from the W

This is the first article in a multi-part series on From Reactive to Proactive: Running Veeam Like a Platform. In the next article, we'll look at the step-by-step process for completing this. Most Veeam environments don’t start out broken.They start out reactive.Something fails → you fix it.A job warns → you investigate it.Storage fills up → you scramble to add more.And for a while, that works.Until it doesn’t.Because as your environment grows, reactive operations turn into:Constant firefighting Unpredictable performance Unclear recovery expectationsAt some point, you realize:You’re not running a backup tool anymore.You’re running a data protection platform.And platforms need to be operated differently. What “Reactive” Actually Looks LikeMost teams don’t realize they’re reactive—it just feels normal.You check

Recently, I was involved in a production support case where a Veeam software appliance deployed on physical hardware failed to boot after an unexpected power interruption.The system dropped directly into:“You are in emergency mode. Cannot open access to console, the root account is locked.”At this point, many administrators assume the appliance is corrupted or that Veeam needs to be reinstalled. In this case, the backup administrator had already reinstalled VBR once, and the issue happened again.  This is not a Veeam software issue. The problem occurs at the Linux storage layer, specifically with LVM and XFS.The Veeam appliance is built on LVM logical volumes formatted with XFS. During boot, Linux must detect storage, activate LVM volume groups, and mount all filesystems defined in

Copy job VM is failing with error server_flat.vmdk either was not backed up successfully or restore chain is corrupted. Failed to download disk server_flat.vmdk The copy job repo is immutable based and cannot delete the single VM from disk ( copy ) so that sync now option can run.The retention set is 30 days and forever incremental is enabled. The VM size is huge and trigerring active full in source backup job will make the old .vbk + .vib to delete only when new .vbk + .vib attains 30 days consuming space in local repo ( non-immutable )Is changing the repo for source backup a feasible option ( would make existing backups to move to new repo ) and then trigger an active full only for the affected VM ?What are the other options available ?

  Veeam participated in HPE Tech Jam Orlando 2026 as a Silver Sponsor, reinforcing its strategic alliance with HPE and underscoring its joint commitment to advancing innovation in cyber resilience and data protection.The Veeam team delivered a special breakout session titled “Securing Your Hybrid Cloud with Veeam and HPE”. The session demonstrated how the Veeam Data Platform integrates seamlessly with HPE Private Cloud and storage solutions to protect hybrid environments, covering virtual, physical, and containerized workloads.Attendees of this session explored the expanding HPE and Veeam partnership, which included new support for HPE Morpheus VM Essentials Software and V13 enhancements across

I am looking for Veeam powershell script to list jobname, server, status and last run for last 24 hours . this should include backup and copy jobs. Kindly assist.

Hello everyone,I have a question regarding MFA in Veeam Host Management.During the initial installation, I enabled MFA on the default veeamadmin account. However, my goal is to use veeamadmin only as a break-glass account and instead create separate admin accounts with MFA enabled.The issue I’m facing is the following:When I enable MFA on another admin account, either:the verification code is sent to the veeamadmin account, or the MFA validation fails completely.This prevents me from properly configuring MFA for individual admin users.Has anyone encountered this behavior?Is there a recommended way to configure MFA for multiple admin accounts while keeping veeamadmin as a fallback account?Thanks in advance for your help.