Community

Choosing the right object storage for backup and ransomware protection is not just about capacity — it’s about immutability, compliance, operational simplicity, and cost predictability.Here’s a clear comparison of three common approaches when using Veeam Backup & Replication: ✅ Veeam Vault (AWS/Azure)Designed as a managed STaaS offering, Veeam Vault delivers always‑on immutability, built‑in encryption, and a logical air‑gap by design. It integrates natively with SOBR and Capacity Tier, offers predictable per‑TB pricing, and removes infrastructure management overhead from the customer. ✅ Native AWS S3 / Azure BlobProvides strong integration and scalability, including Object Lock / immutable containers and support for compliance mode. However, immutability and air‑gap depend heavily on correct configuration, IAM design, and governance. Pricing is consumption‑based, which can introduce cost variability (“bill shock”). ⚠️ OCI Object Storage (S3‑compatible)While usable as an S3‑compatib

Dear AllGreetings!!!I fany one face this issue please let me know.Server Error in Veeam one - One or more critical product files have been modified. Please roll back the changes, or reinstall the product.After login into Web console of Veeam One i am getting this error message.Running Version is : 13.0.1.6168 

HelloI am experiencing a behavior that seems unusual compared to my previous experiences. I have three Tape pools with different retention policies. When I try to move a tape from one of these pools to the 'Free' pool, I receive a notification stating that moving the tape will cause it to be formatted.Is this normal behavior? Additionally, how can I remove a tape from a pool without it being formatted?

Backups without notifications are like monitoring without alerting: you can live with it—until the day you can’t.Veeam Backup & Replication (VBR) and Veeam Backup Enterprise Manager (VEM) can send automated emails, for example when an event is triggered, like:Job success/warning/failure  Infrastructure warnings Licensing/support notificationsThe goal: you find out about problems as soon as they happen.(And yes: “no news” are also news—but only if you’re sure your email delivery is actually working.) Veeam Doku: E-Mail-Settings & Notifications (VBR v13)https://helpcenter.veeam.com/docs/vbr/userguide/pve_email_settings.html?ver=13VEM Doku: Email-Settings & Notification (v13)https://helpcenter.veeam.com/docs/vbr/em/notifications_ms365.html?ver=13 “Can’t I just enter an SMTP server + username/password and be done with it?” For several years, that was actually the only way—and of course it can still work today. This classic approach is called SMTP server (basic authentication).V

In Part 1, we talked about the difference between reactive and proactive Veeam operations.But knowing the difference is the easy part. The real question is:How do you actually make the transition—without overhauling everything at once?Because most environments can’t just stop and rebuild.They have to evolve.This is how you do it—step by step, without creating more chaos in the process. Step 1: Get Visibility (You Can’t Fix What You Can’t See)Before you change anything, you need a clear picture of where you are.Start with:Job success vs warning vs failure rates Backup job durations (are they increasing?) Repository capacity and growth rate Restore success history (if any exists)The goal:Understand your baseline.Not what you think is happening—what’s actually happening.Proactive operations start with awareness. Step 2: Clean Up the NoiseMost reactive environments have one thing in common:Too many alerts. Too many warnings. Too much noise.Do this next:Review all current warnings Fix what

 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 0 errors (verified recoverability)✔️ This model protects against hardware failure✔️ It addresses human error✔️ It covers traditional disaster scenariosBut here’s the reality:⚠️ Attackers now design their operations specifically to break this model.What Changed? (And Why It Matters)1. Backups Are the First TargetModern ransomware attacks:Target backup servers first Delete or corrupt backup chains Exploit APIs and credentialsBa

 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 user has insufficient privileges.This meant that we were locked out immediately after installation.   Troubleshooting: A look behind the scenesAfter a short analysis, it was clear: We won't get anywhere with the web UI at this point. So we decided without further ado to take a targeted look at VRO's SQL database

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), port customization concepts, and High Availability with VSA HA cluster setup plus Veeam ONE monitoring using alarms/dashboards and REST API automation. The list also includes practical h

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 github repo and with the help of claude containerized it. THIS IS NOT MEANT FOR PRODUCTION! Just for Lab Learning! Clone Luca’s repo on your podman host: git clone https://github.com/dellock6/pykmip-veea

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 Image-Level Backup RMAN Plug-in Backup scope Entire VM or volume (includes OS, Oracle binaries, database) Database only (data files, control files, archived logs) Point-in-time restore

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 email from Veeam to register mike.mckenney@scsirai

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 data emergencies don't respect holidays. The moment we received the aler

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 objects such as clusters, hosts, VMs, folders, resource pools, tags, roles/permissions, HA/DRS, and many automation features. For backup solutions, vCenter is important because it provides a stable, always up-to-date inventory and object referencing ID (keyword: MoRef).  Moe? Like that bartender from The Simpsons?  Äh no — tha

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 summary report on completed Company2 backup jobs to 2 email addresses – company2user@domain.

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 database (PostgreSQL in v13, formerly SQL Server Express) and the file system logs. Database (Session and Task Records) Eve

 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 Windows Start menu, or through PowerShell. Opening the tool is easy. The part that matters is

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 failures after they happen You deal with warnings when they pile up You only look at performance when it’s slow You test restores when someone asksNothing is technically “wrong.”B

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 /etc/fstab before any services start.If any of these steps fail, the system enters emergency mode to protect itself. This is a safety mechanism, not a catastrophic failure.Understanding this boot sequence ma