Community

When running self-hosted applications in a homelab or on-premises environment, HTTPS is often the first thing to fall through the cracks. Self-signed certificates trigger browser warnings, and public certificate authorities like Let's Encrypt require your services to be internet-accessible. The solution? Run your own internal Certificate Authority.However, this is not a difficult problem to solve. Just setup an internal PKI using Step CA running as a rootless Podman container, then extend it to issue certificates for services on your network. In this first part, we'll focus entirely on getting Step CA up and running — initializing the CA, configuring automated certificate issuance, and setting up a systemd timer to handle renewals without any manual intervention.Create a new podman network for step-capodman network create ca-servicespodman network lsCreate a CA volume and Quadlet (quadlets are the preferred m

One of my VM is showing  FIB summary.txt issue in backup copy job. I would like to run Active full backup on only this problem VM . But this backup copy job has 20 VMs which i don’t want to run full backup as it will cause issue in wasabi bucket. Copy job goes to wasabi bucket. I know individual full backup can initiated in Backup job, but it is not showing BCJ . Please advise.Ver 12.1.2

With the High Availability feature in Veeam Software Appliance 13.0.1, Veeam provides a neat way to make the backup server highly available. In this blog post I’ll briefly show how to configure HA, which prerequisites must be met, and what alternatives exist if HA cannot be used. Intro - The Basics The feature itself reduces downtime of the backup server in the Veeam Software Appliance. In general, two nodes are required; they can synchronize even across relatively high latencies. A manual switchover is possible, and a major advantage is automatic updates for both nodes. The goal is to offer fast disaster recovery without the need to keep a dedicated standby backup server, and then finally to restore the configuration backup. 

In the final article of this three-part series, we’ll explore how proactive operations with Veeam can help organizations reduce downtime and enhance data protection.By the time you reach this point, things feel different.You’re no longer chasing failures.You’re no longer guessing recovery times.You’re not constantly reacting to alerts.Instead, your Veeam environment starts to feel… predictable.That’s the goal.But scaling proactive operations isn’t just doing the same things on a bigger environment.It’s about operating with intention, consistency, and confidence—no matter how large things get.This is what that actually looks like in practice. 1. Health Is Measured, Not AssumedAt scale, you don’t rely on “it looks fine.”You rely on metrics and trends.What you know at any given time:Job success and warning rates Backup

Microsoft BitLocker Administration and Monitoring (MBAM) and Advanced Group Policy Management (AGPM), both part of the Microsoft Desktop Optimization Pack (MDOP), have officially reached end of support as of 14 April 2026 (today). From this point forward, Microsoft will no longer provide security updates, bug fixes, or compatibility assurances for these tools, similar to the lifecycle outcome observed with Microsoft Deployment Toolkit (MDT).Organizations that continue to rely on MBAM and AGPM must now assess risk exposure, validate operational dependencies, and define a transition strategy toward supported alternatives to maintain security, compliance, and long-term manageability.To help you transition away from MBAM and AGPM, I have outlined practical and supported alternatives in the following guides

Need to pull a report of protected servers along with job names for which the application aware processing is enabled  We have Veeam one / can use script option , backup version 13  

IntroductionTo enable monitoring of your Veeam Software Appliance (VSA) with VeeamONE, the Veeam Analytics Service needs to be deployed on the VSA.The Veeam Analytics service not only enables communication with Veeam Backup & Replication servers to collect data but also allows to send remediation commands.Since the VSA is secure by design (hardened Linux-based OS, DISA STIG compliance, automated patching…) and that it enforces Zero Trust principles with role-based access control

USB drive used as copy job repo is having input / output error, cannot open the drive in the server 

Just wanted to know How Veeam support Openstack and Hypervisor for VMware

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

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=13

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

 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